Java Platform, Enterprise Edition (Java EE) 8
The Java EE Tutorial
In addition to the lifecycle description, an overview of JavaServer Faces architecture provides better understanding of the technology.
JavaServer Faces components are the building blocks of a JavaServer Faces view. A component can be a user interface (UI) component or a non-UI component.
JavaServer Faces UI components are configurable, reusable elements that compose the user interfaces of JavaServer Faces applications. A component can be simple, such as a button, or can be compound, such as a table composed of multiple components.
JavaServer Faces technology provides a rich, flexible component architecture that includes the following:
A set of
javax.faces.component.UIComponent classes for specifying
the state and behavior of UI components
A rendering model that defines how to render the components in various ways
A conversion model that defines how to register data converters onto a component
An event and listener model that defines how to handle component events
A validation model that defines how to register validators onto a component
This section briefly describes each of these pieces of the component architecture.
JavaServer Faces technology provides a set of UI component classes and associated behavioral interfaces that specify all the UI component functionality, such as holding component state, maintaining a reference to objects, and driving event handling and rendering for a set of standard components.
The component classes are completely extensible, allowing component writers to create their own custom components. See Chapter 15, "Creating Custom UI Components and Other Custom Objects" for more information.
The abstract base class for all components is
javax.faces.component.UIComponent. JavaServer Faces UI component
classes extend the
UIComponentBase class (a subclass of
UIComponent), which defines the default state and behavior of a
component. The following set of component classes is included with
JavaServer Faces technology.
UIColumn: Represents a single column of data in a
UICommand: Represents a control that fires actions when activated.
UIData: Represents a data binding to a collection of data
represented by a
UIForm: Represents an input form to be presented to the user. Its
child components represent (among other things) the input fields to be
included when the form is submitted. This component is analogous to the
form tag in HTML.
UIGraphic: Displays an image.
UIInput: Takes data input from a user. This class is a subclass of
UIMessage: Displays a localized error message.
UIMessages: Displays a set of localized error messages.
UIOutcomeTarget: Displays a link in the form of a link or a button.
UIOutput: Displays data output on a page.
UIPanel: Manages the layout of its child components.
UIParameter: Represents substitution parameters.
UISelectBoolean: Allows a user to set a
boolean value on a control
by selecting or deselecting it. This class is a subclass of the
UISelectItem: Represents a single item in a set of items.
UISelectItems: Represents an entire set of items.
UISelectMany: Allows a user to select multiple items from a group of
items. This class is a subclass of the
UISelectOne: Allows a user to select one item from a group of items.
This class is a subclass of the
UIViewParameter: Represents the query parameters in a request. This
class is a subclass of the
UIViewRoot: Represents the root of the component tree.
In addition to extending
UIComponentBase, the component classes also
implement one or more behavioral interfaces, each of which defines
certain behavior for a set of components whose classes implement the
These behavioral interfaces, all defined in the
package unless otherwise stated, are as follows.
ActionSource: Indicates that the component can fire an action event.
This interface is intended for use with components based on JavaServer
Faces technology 1.1_01 and earlier versions. This interface is
deprecated in JavaServer Faces 2.
ActionSource and therefore provides the
same functionality. However, it allows components to use the Expression
Language (EL) when they are referencing methods that handle action
ValueHolder and specifies additional
features for editable components, such as validation and emitting
NamingContainer: Mandates that each component rooted at this
component have a unique ID.
StateHolder: Denotes that a component has state that must be saved
ValueHolder: Indicates that the component maintains a local value as
well as the option of accessing data in the model tier.
javax.faces.event.SystemEventListenerHolder: Maintains a list of
javax.faces.event.SystemEventListener instances for each type of
javax.faces.event.SystemEvent defined by that class.
javax.faces.component.behavior.ClientBehaviorHolder: Adds the
ability to attach
instances, such as a reusable script.
component classes that extend
UIInput and component classes that extend
Only component writers will need to use the component classes and
behavioral interfaces directly. Page authors and application developers
will use a standard component by including a tag that represents it on a
page. Most of the components can be rendered in different ways on a
page. For example, a
UICommand component can be rendered as a button
or a link.
The next section explains how the rendering model works and how page authors can choose to render the components by selecting the appropriate tags.
The JavaServer Faces component architecture is designed such that the functionality of the components is defined by the component classes, whereas the component rendering can be defined by a separate renderer class. This design has several benefits, including the following.
Component writers can define the behavior of a component once but create multiple renderers, each of which defines a different way to render the component to the same client or to different clients.
Page authors and application developers can change the appearance of a component on the page by selecting the tag that represents the appropriate combination of component and renderer.
A render kit defines how component classes map to component tags that are appropriate for a particular client. The JavaServer Faces implementation includes a standard HTML render kit for rendering to an HTML client.
The render kit defines a set of
for each component that it supports. Each
Renderer class defines a
different way to render the particular component to the output defined
by the render kit. For example, a
UISelectOne component has three
different renderers. One of them renders the component as a group of
options. Another renders the component as a combo box. The third one
renders the component as a list box. Similarly, a
can be rendered as a button or a link, using the
h:commandLink tag. The
command part of each tag corresponds to the
UICommand class, specifying the functionality, which is to fire an
Link part of each tag corresponds to a
Renderer class that defines how the component appears on the
Each custom tag defined in the standard HTML render kit is composed of
the component functionality (defined in the
UIComponent class) and the
rendering attributes (defined by the
The section Adding Components to a Page Using HTML Tag Library Tags lists all supported component tags and illustrates how to use the tags in an example.
The JavaServer Faces implementation provides a custom tag library for rendering components in HTML.
A JavaServer Faces application can optionally associate a component with server-side object data. This object is a JavaBeans component, such as a managed bean. An application gets and sets the object data for a component by calling the appropriate object properties for that component.
When a component is bound to an object, the application has two views of the component’s data.
The model view, in which data is represented as data types, such as
The presentation view, in which data is represented in a manner that
can be read or modified by the user. For example, a
might be represented as a text string in the format
mm/dd/yy or as a
set of three text strings.
The JavaServer Faces implementation automatically converts component
data between these two views when the bean property associated with the
component is of one of the types supported by the component’s data. For
example, if a
UISelectBoolean component is associated with a bean
property of type
java.lang.Boolean, the JavaServer Faces
implementation will automatically convert the component’s data from
Boolean. In addition, some component data must be bound to
properties of a particular type. For example, a
component must be bound to a property of type
Sometimes you might want to convert a component’s data to a type other
than a standard type, or you might want to convert the format of the
data. To facilitate this, JavaServer Faces technology allows you to
javax.faces.convert.Converter implementation on
components and components whose classes subclass
UIOutput. If you
Converter implementation on a component, the
implementation converts the component’s data between the two views.
You can either use the standard converters supplied with the JavaServer Faces implementation or create your own custom converter. Custom converter creation is covered in Chapter 15, "Creating Custom UI Components and Other Custom Objects".
The JavaServer Faces event and listener model is similar to the JavaBeans event model in that it has strongly typed event classes and listener interfaces that an application can use to handle events generated by components.
The JavaServer Faces specification defines three types of events: application events, system events, and data-model events.
Application events are tied to a particular application and are
generated by a
UIComponent. They represent the standard events
available in previous versions of JavaServer Faces technology.
An event object identifies the component that generated the event and stores information about the event. To be notified of an event, an application must provide an implementation of the listener class and must register it on the component that generates the event. When the user activates a component, such as by clicking a button, an event is fired. This causes the JavaServer Faces implementation to invoke the listener method that processes the event.
JavaServer Faces supports two kinds of application events: action events and value-change events.
An action event (class
javax.faces.event.ActionEvent) occurs when the
user activates a component that implements
components include buttons and links.
A value-change event (class
when the user changes the value of a component represented by
or one of its subclasses. An example is selecting a check box, an action
that results in the component’s value changing to
true. The component
types that can generate these types of events are the
Value-change events are fired only if no validation errors are detected.
Depending on the value of the
immediate property (see
The immediate Attribute) of the component
emitting the event, action events can be processed during the Invoke
Application phase or the Apply Request Values phase, and value-change
events can be processed during the Process Validations phase or the
Apply Request Values phase.
System events are generated by an
Object rather than a
They are generated during the execution of an application at predefined
times. They are applicable to the entire application rather than to a
A data-model event occurs when a new row of a
UIData component is
There are two ways to cause your application to react to action events or value-change events that are emitted by a standard component:
Implement an event listener class to handle the event, and register
the listener on the component by nesting either an
f:valueChangeListener tag or an
f:actionListener tag inside the
Implement a method of a managed bean to handle the event, and refer to the method with a method expression from the appropriate attribute of the component’s tag.
See Referencing a Managed Bean Method for information on how to refer to the managed bean method from the component tag.
When emitting events from custom components, you must implement the appropriate event class and manually queue the event on the component in addition to implementing an event listener class or a managed bean method that handles the event. Handling Events for Custom Components explains how to do this.
JavaServer Faces technology supports a mechanism for validating the local data of editable components (such as text fields). This validation occurs before the corresponding model data is updated to match the local value.
Like the conversion model, the validation model defines a set of
standard classes for performing common data validation checks. The
JavaServer Faces core tag library also defines a set of tags that
correspond to the standard
implementations. See Using the Standard
Validators for a list of all the standard validation classes and
Most of the tags have a set of attributes for configuring the validator’s properties, such as the minimum and maximum allowable values for the component’s data. The page author registers the validator on a component by nesting the validator’s tag within the component’s tag.
In addition to validators that are registered on the component, you can
declare a default validator that is registered on all
components in the application. For more information on default
validators, see Using Default
The validation model also allows you to create your own custom validator and corresponding tag to perform custom validation. The validation model provides two ways to implement custom validation.
Validator interface that performs the validation.
Implement a managed bean method that performs the validation.
If you are implementing a
Validator interface, you must also do the
Validator implementation with the application.
Create a custom tag or use an
f:validator tag to register the
validator on the component.
In the previously described standard validation model, the validator is defined for each input component on a page. The Bean Validation model allows the validator to be applied to all fields in a page. See Chapter 23, "Introduction to Bean Validation" and Chapter 24, "Bean Validation: Advanced Topics" for more information on Bean Validation.