JSF Tutorials

11. Install and Deploy JBoss Application Server

By: Abinaya : 2007-09-18

Description: In this tutorial let's go over the process to setup JBoss application server to run web applications.

12. Controlling Page Navigation in JSF - Static and Dynamic Navigation

By: Jagan : 2007-09-18

Description: Page navigation in your JSF application is handled by providing navigation rules in a configuration file. The navigation can specify which web component initiates the request, which web component handles the response, and which value causes navigation to follow the flow. So far, you have seen only navigation based on the hard-coded string value of an action attribute. You can also control navigation by using value-binding expressions and method-binding expressions. Navigation then depends on the value of the expression.

13. Java Bean Scopes in JSF

By: Ivan Lim : 2007-09-18

Description: When you configure a JavaBean to be used in a JSF page, you can configure it with one of four

14. Installing JSF

By: Grenfel : 2007-09-18

Description: You will need to obtain and install a JSF implementation, and the JSP Standard Tag Library (JSTL) reference implementation. We will use the JSF reference implementation from Sun. If you have an implementation from some other vendor, consult the documentation for that implementation for installation instructions.

15. JSF Life Cycle

By: Fazal : 2007-09-18

Description: Regardless of whether you are using JSF with JSP pages, servlets, or some other web technology, each request/response flow that involves JSF follows a certain life cycle. Several kinds of request/response cycles can occur in a JSF-enabled application. You can have a request that comes from a previously rendered JSF page (a JSF request) and a request that comes from a non-JSF page (a non-JSF request). Likewise, you can have a JSF response or a non-JSF response. We are concerned with these three request/response pairs:

16. The Relationship Between JSF and Other Java EE Technologies

By: Emiley J : 2007-09-18

Description: Within the Java Platform, Enterprise Edition 5 (Java EE 5), technologies such as JSP and Servlet are stand-alone technologies. You could, if you wanted to, create an application using only servlets or only JSP pages. JSF is different because it is a supporting technology. You use it in conjunction with JSP pages, servlets, or other presentation technologies.

17. JSF Basics

By: Daniel Malcolm : 2007-09-18

Description: UI development is easier because UI components are provided as reusable objects. A number of classes, corresponding to UI components, are part of the JSF specification and implementation. Rather than have to worry about the syntax of page layout, you simply drop the UI components into your application. A custom render kit and rendering process convert the components into appropriate page-layout code. The JSF implementation comes with a default render kit for HTML, but the same JSF code can be rendered by other render kits for other client systems. This means that you can use the same JSF code for a variety of client systems, and use different render kits to customize the UI for each client system.

18. Differences between JavaServer Faces technology and Struts

By: Charles : 2007-09-18

Description: Struts is an open-source Java web application framework whose architecture is based on the Model-View-Controller design pattern in which requests are routed through a controller that provides overall application management and dispatches the requests to application components. JavaServer Faces technology is a user-interface framework for Java web applications. It is focussed on the view tier of an MVC-based architecture. The Struts and JavaServer Faces technology frameworks do have some overlapping functionality; however each framework has its advantages, and developers can use certain features of both frameworks in a single application.

19. What is JSF (JavaServer Faces)?

By: Baski : 2007-09-18

Description: A complete web application requires a web framework to generate HTML pages, receive user input, and manage the navigation flow. The consensus among most web developers is that a Model-View-Controller (MVC) architecture is the best for web frameworks. In an MVC framework, the controller takes user input and decides which view to show next; The view renders the HTML page for the browser; The model encapsulates data captured from the web form and to be displayed on the web page.