Java Server Faces (JSF)

Java Server Faces (JSF)

JSF is used for building Java Web application interfaces. Like Swing and AWT, JSF is a development framework that provides a set of standard, reusable GUI components. JSF provides the following development advantages:

Clean separation of behavior and presentation Component-level control over statefulness Events easily tied to server-side code Leverages familiar UI-component and Web-tier concepts Offers multiple, standardized vendor implementations JSF's fine-tuned event model allows your applications to be less tied to HTTP details and simplifies your development effort.

Java Server Faces (JSF)

A typical JSF application consists of the following parts:

JavaBeans components for managing application state and behavior Event-driven development (via listeners as in traditional GUI development) Pages that represent MVC-style views; pages reference view roots via the JSF component tree

JSF MVC Design

The model-view-controller (MVC) architecture provides a set of design patterns that help you separate the areas of concern involved in building and running a GUI-based application:

The model encapsulates the business logic and persistence code for the application. The model should be as view-technology-agnostic as possible. For example, the same model should be usable with a Swing application, a Struts application, or a JSF application. The view should display model objects and contain presentation logic only. There should be no business logic or controller logic in the view. The controller (along with its attending logic) acts as the mediator between the view and the model. The controller talks to the model and delivers model objects to the view to display. In an MVC architecture the controller always selects the next view.

JSF MVC Implementation

In JSF's MVC implementation, backing beans mediate between the view and the model. Because of this, it's important to limit the business logic and persistence logic in the backing beans. One common alternative is to delegate business logic to a faade that acts as the model. Unlike JSP technology, JSF's view implementation is a stateful component model. The JSF view is comprised of two pieces: the view root and JSP pages.

The view root is a collection of UI components that maintain the state of the UI The JSP page binds UI components to JSP pages and allow you to bind field components to properties of backing beans

JSF MVC Implementation

JSF Example

JSF Example
1. 2. 3. 4. 5. 6. 7. 8.

To build the Calculator application in JSF you'll need to do the following: Declare the Faces Servlet, and Faces Servlet mapping in the [Link] file. Declare what beans get managed by JSF in the [Link] file. Declare the navigation rules in the [Link] file. Develop the model object Calculator. Use the CalculatorController to talk to the Calculator model. Create the [Link] page. Create the [Link] page. Create the [Link] page.

Declare the Faces Servlet and Servlet mapping

<!-- Faces Servlet --> <servlet> <servlet-name>Faces Servlet</servlet-name> <servlet-class>[Link]</servlet-class> <load-on-startup> 1 </load-on-startup> </servlet>

<!-- Faces Servlet Mapping --> <servlet-mapping> <servlet-name>Faces Servlet</servlet-name> <url-pattern>/calc/*</url-pattern> </servlet-mapping>

The above tells the Faces Servlet container to send all requests that map to /calc/ to the Faces Servlet for processing.

Declare bean management

Next, you will want to declare which beans get used by JSF GUI components. The example application only has one managed bean. It is configured in [Link] as follows:
<faces-config> ... <managed-bean> <description> The "backing file" bean that backs up the calculator webapp </description> <managed-bean-name>CalcBean</managed-bean-name> <managed-bean-class>[Link]</managed-bean-class> <managed-bean-scope>session</managed-bean-scope> </managed-bean> </faces-config>

The above config tells JSF that you want to add a bean to the JSF context called CalcBean. You can call your managed bean anything you want.

Declare navigation rules

For this simple application you need only to establish the navigation path from the [Link] page to the [Link] page, as shown below.
<navigation-rule> <from-view-id>/[Link]</from-view-id> <navigation-case> <from-outcome>success</from-outcome> <to-view-id>/[Link]</to-view-id> </navigation-case> </navigation-rule>

Develop the model object

package [Link]; public class Calculator { //add numbers.
public int add(int a, int b) {
return a + b;

} // multiply numbers public int multiply(int a, int b) {

return a * b;

} With that, the business logic is all set up. Your next step is to glue it to the Web application interface.

Gluing the model and the view through the controller

package [Link]; import [Link]; public class CalculatorController { private Calculator calculator = new Calculator(); private int firstNumber = 0; private int result = 0; private int secondNumber = 0; public CalculatorController() {super(); } public void setCalculator(Calculator aCalculator) { [Link] = aCalculator; } public void setFirstNumber(int aFirstNumber) { [Link] = aFirstNumber; } public int getFirstNumber() { return firstNumber; } public int getResult() { return result; } public void setSecondNumber(int aSecondNumber) { [Link] = aSecondNumber; } public int getSecondNumber() { return secondNumber; } public String add() { result = [Link](firstNumber, secondNumber); return "success"; } public String multiply() { result = [Link](firstNumber, secondNumber); return "success"; } }

Gluing the model and the view through the controller

package [Link]; import [Link]; public class CalculatorController { private Calculator calculator = new Calculator(); private int firstNumber = 0; private int result = 0; private int secondNumber = 0; public CalculatorController() {super(); } public void setCalculator(Calculator aCalculator) { [Link] = aCalculator; } public void setFirstNumber(int aFirstNumber) { [Link] = aFirstNumber; } public int getFirstNumber() { return firstNumber; } public int getResult() { return result; } public void setSecondNumber(int aSecondNumber) { [Link] = aSecondNumber; } public int getSecondNumber() { return secondNumber; } public String add() { result = [Link](firstNumber, secondNumber); return "success"; } public String multiply() { result = [Link](firstNumber, secondNumber); return "success"; } }

Notice that the multiply and add methods return "success." The string success signifies a logical outcome. Note that it is not a keyword. You used the string success when specifying navigation rules in [Link]; therefore, after the add or multiply operation is executed the application will forward the user to the [Link] page. With that, you're done with the backing code. Next you'll specify the JSP pages and component trees that represent the application view.

Create the [Link] page

The purpose of the [Link] page in this application is to ensure that the /[Link] page loads in the JSF context so that the page can find the corresponding view root. The [Link] page looks as follows:

<jsp:forward page="/calc/[Link]" />

All this page does is redirect the user to [Link] under the "calc" Web context. This puts the [Link] page under the JSF context, where it can find its view root.

Create the [Link] page

<%@ taglib uri="[Link] prefix="h" %> <%@ taglib uri="[Link] prefix="f" %>
<f:view> <h:form id="calcForm"> <h:panelGrid columns="3"> <h:outputLabel value="First Number" for="firstNumber" /> <h:inputText id="firstNumber" value="#{[Link]}" required="true" /> <h:message for="firstNumber" /> <h:outputLabel value="Second Number" for="secondNumber" /> <h:inputText id="secondNumber" value="#{[Link]}" required="true" /> <h:message for="secondNumber" /> </h:panelGrid>

<h:panelGroup> <h:commandButton id="submitAdd" action="#{[Link]}" value="Add" /> <h:commandButton id="submitMultiply" action="#{[Link]}" value="Multiply" /> </h:panelGroup>
</h:form> </f:view>

Create the [Link] page

<%@ taglib uri="[Link] prefix="h" %> <%@ taglib uri="[Link] prefix="f" %> <f:view> First Number: <h:outputText id="firstNumber" value="#{[Link]}"/> <br /> Second Number: <h:outputText id="secondNumber" value="#{[Link]}"/> <br /> Result: <h:outputText id="result" value="#{[Link]}"/> <br /> </f:view>

This [Link] file is a relatively simplistic page that displays the addition results to the user. It accomplishes this through the <outputText> tag. The <outputText> tag takes an id and value attribute. The value attribute outputs the bean value as a string when rendered. The value attribute uses JSF to bind the output value to your backing bean properties (namely, firstNumber, secondNumber, and result).

Demo with NetBeans 5.5 and the Visual Web Pack

Read Visual Web Pack documentation for details with more emphasis of the following: - Layout: Property Sheets, JSF Fragments - Data Binding: CachedRowSet, CachedRowSetDataProvider, ObjectListDataProvider

JSF Request Processing Lifecycle

Response Complete Response Complete

Request

Restore Component Tree

Apply Request Value

Process Events

Process Validations

Process Events

Render Response Response Complete

Response Render Response Process Events Invoke Application

Response Complete
Process Events Update Model Values

Conversion Errors

Validation or Conversion Errors

JSF - Request Processing Lifecycle

Restore component tree

The controller examines the request and extracts the view ID, which is determined by the name of the JSP page. If the view doesn't already exist, the JSF controller creates it. If the view already exists, the JSF controller uses it. The view contains all the GUI components. The purpose of the apply request values phase is for each component to retrieve its current state. Component values are typically retrieved from the request parameters. At this stage, each component will have its values validated against the application's validation rules. updates the actual values of the server-side model -- namely, by updating the properties of your backing beans.

Apply Request Values

Process Validations

Update Model

JSF - Request Processing Lifecycle

Invoke Application
The

JSF controller invokes the application to handle Form submissions. The component values will have been converted, validated, and applied to the model objects, so you can now use them to execute the application's business logic.

Render Response
you

display the view with all of its components in their current state. Render the page and send it back to client

JSF Component
Model binds Event Handling has Render

has UIComponent has

Id Local Value Attribute Map

has

has has

Validators

Child UIComponent

Converters

JSF Standard UI Components

UIInput UIOutput UISelectBoolean UISelectItem UISelectMany UISelectOne UISelectMany UIGraphic

UICommand UIForm UIColumn UIData UIPanel

JSF HTML Tag Library

JSF Core Tag Library

Validator,

Event Listeners, and Converters

JSF Standard Library

Express

UI components in JSP

JSF HTML Tag Library

<f:view> <h:form id=logonForm> <h:panelGrid columns=2> <h:outputLabel for=username> <h:outputLext value=Username:/> </h:outputLabel> <h:inputText id=username value=#{[Link]}/> <h:outputLabel for=password> <h:outputText value=Password:/> </h:outputLabel> <h:inputSecret id=password value=#{[Link]}/> <h:commandButton id=submitButton type=SUBMIT action=#{[Link]}/> <h:commandButton id=resetButton type=RESET/> </h:panelGrid> </h:form> </f:view>

JSF HTML Tag Library

<table> <tr><td>Food Selection:</td></tr> <tr><td> <h:selectManyCheckBox value=#{[Link]}> <f:selectItem itemValue=z itemLabel=Pizza /> <f:selectItem itemValue=fc itemLabel=Fried Chicken /> <f:selectItem itemValue=h itemLabel=Hamburger /> </h:selectManyCheckBox> </td> </table>

JSF Rendering Model

Two Rendering Models (direct or delegated) Direct Decoding Encoding Delegated Renderer Component

Pluggable look and feel

JSF Rendering Model

Render kit consists of a set of renders JSF reference implement must provide a render kit for all the standard UI components to generate HTML 4.01 Custom render kit can be provided to render UI components into a specific markup language

JSF Managed Bean

Use to separate presentation from business logic Based on JavaBeans Use the declarative model Entry point into the model and event handlers

JSF Value Binding

Bind

component value and attribute to model objects

Literal: <h:outputText rendered=true value=$1000.00/> Value Binding: <h:outputText rendered=#{[Link]} value=#{[Link]}/>

JSF Value Binding

Value binding expression

Bean List Array Map Predefine

properties

objects- header, header values, request parameters, cookie, request/session/application scope attributes, initial parameters

JSF Value Binding Expression

<h:outputText value=#{[Link]} /> <h:outputText value=Hello There #{[Link]} /> #{![Link]} operator (+, -, *, /, % ) [Link] <managed-bean> <managed-bean-name>user</managed-bean-name> <managed-bean-class>[Link]</managed-bean-class> <managed-bean-scope>session</managed-bean-scope> </managed-bean> Support bean property initialization for primitive data type as well as List and Map. Binding expression can be used at the bean configuration at well

JSF Predefined Objects

Variable
header headerValues param paramValues cookie initParam requestScope sessionScope applicationScope facesContext view

Meaning
A Map of HTTP headers, only the first value of for each name A Map of HTTP headers, String[] of all values for each name A Map of HTTP request parameters, first value of for each name A Map of HTTP headers, String[] of all values for each name A Map of cookie name and values A Map of initialization parameters A Map of all request scope attributes A Map of all session scope attributes A Map of all request scope attributes FacesContext instance of this request The UIViewRoot instance of this request

JSF Method Binding

Binding an event handler to a method

<h:commandButton action=#{[Link]} />

Four component attributes:

Action Action

listener Value change listener Validator

JSF Events
Events are fired by each UI component Event handlers are registered with each component

JSF Events Value Change Event

Value Changed Listener:
<h:inputText id=maxUsers valueChangeListener=#{[Link]} /> public void checkMaxUser(ValueChangeEvent evt) { [Link](); // new value [Link](); // old value }

JSF Events Action Event

Action Listener:
<h:commandButton value="Login actionListener=#{[Link]} action=#{[Link]} /> public void loginActionListener(ActionEvent e) { } public String login() { return OK; // return FAI; }

JSF Events Listener vs. Action

Listener Handlers
Implement

UI logic Have access to event source Do not participate in navigation handling

Action Handlers
Implement

business logic Dont have access to action source Returned outcome affects the navigation handling

JSF Multiple Event Handlers

<h:selectOneMenu value=#{[Link]} <f:valueChangeListener type=[Link] <f:valueChangeListener type=[Link] </h:selectionOneMenu> <h:commandButton action=#{[Link]()}> <f:actionListener type=[Link] /> <f:actionListener type=[Link] /> </h:commandButton>

JSF Validators
For validating user input 0 or more validators can be registered with a UIInput component Validators are invoked during the Process Validations request processing phase Standard validators and custom validator

JSF Two Step Approach

Request Apply Request Value

Submitted Value

Validation Y Local Value

Model Value

N Conversion

JSF Validators

DoubleRangeValidator
Any

numeric type, between specified maximum and minimum values numeric type convertible to long, between specified maximum and minimum values type, between specified maximum and minimum values

LongRangeValidator
Any

LengthValidator
String

JSF Validators
Required Validation Example: <h:inputText value=#{[Link]} required=true /> Length Validation Example: <h:inputText value=#{[Link]} > <f:validateLength minimum=6 /> <f:validator validatorId=passwordValidator /> </h:inputText>

JSF Converters
Type conversion between server-side objects and their representation in markup language Standard converter implementations

DateTime Number

JSF Converters
Number converter example: <h:inputText value=#{[Link]} converter=Number> <f:attribute name=numberStyle value=currency /> </h:inputText> Date convert example: <h:inputText value=#{[Link]} converter=DateFormat> <f:attribute name=formatPattern value=MM/DD /> </h:inputText>

JSF Navigation
JSF provides a default navigational handler Behavior is configured in configuration file ([Link])

Navigation
1 Contains * Navigation Rule

has
1 Contains *

From View Id

Navigation Case

JSF Navigation - Example

<navigation-rule>
<description>LOGIN PAGE NAVIGATION HANDLING</description> <from-view-id> /[Link] </from-view-id> <navigation-case> <description>Handle case where login succeeded.</description> <display-name>Successful Login</display-name> <from-action>#{[Link]}</from-action> <from-outcome>success</from-outcome> <to-view-id>/[Link]</to-view-id> </navigation-case> <navigation-case> <description>User registration for a new user succeeded.</description> <display-name>Successful New User Registration</display-name> <from-action>#{[Link]}</from-action> <from-outcome>success</from-outcome> <to-view-id>/[Link]</to-view-id> </navigation-case>

</navigation-rule>

JSF Error Handling

[Link] Information, Warning, Error, Fatal

Contain summary and detail <h:messages> - to display all messages <h:message> - to display a single message for a particular component [Link] sage(String clientId, FacesMessage)

JSF - HTML & CSS Integration

HTML Integration
Pass-through

attributes <h:inputText size=5 onblur=checkValue(); />

Stylesheets Integration
Most

HTML tags have one or more attributes (style, styleClass) for passing style information

<h:outputText styleClass=header value=#{[Link]} /> For data table

<h:dataTable rowClasses=odd, even, columnClasses=columnOne, columnTwo ..

References

JavaServer Faces 1.0 (JSR-127) Tour, Hien Luu, Neoforma [Link], Visual Web Pack Documentation