JBoss.orgCommunity Documentation

Chapter 3. RichFaces overview

3.1. Full technical requirements
3.1.1. Server requirements
3.1.2. Client requirements
3.1.3. Development requirements
3.2. Architecture
3.2.1. Ajax Action Components
3.2.2. Ajax Containers
3.2.3. Ajax Output
3.2.4. Skins and theming
3.2.5. RichFaces Ajax Extensions
3.3. Technologies
3.4. Differences between JSF and RichFaces mechanisms
3.5. Restrictions

Read this chapter for technical details on the RichFaces framework.

RichFaces has been developed with an open architecture to be compatible with a wide variety of environments.

The important elements of the RichFaces framework are as follows:

Read this section for details on each element.

RichFaces 4 features full JSF 2 integration and uses standard web application technologies such as JavaScript, XML (Extensible Markup Language), and XHTML (Extensible Hypertext Markup Language).

JavaServer Faces 2 evaluates Ajax options, such as execute and render, while rendering a page. This allows any parameters to be sent directly from the client side.

RichFaces evaluates the options when the current request is sent. This increases both the security of the data and the convenience for evaluating parameters.

For example, binding Ajax options to Java Bean properties in RichFaces allows you to evaluate the options dynamically for the current request, such as defining additional zones to render. Parameters changed manually on the client side will not influence the request processing. With JSF 2, the options have evaluated during the previous page rendering would need to be used.

The following restrictions apply to applications implementing the RichFaces framework: