RichFaces
Screenshot 
Design by JBoss
Latest release 3.2.2 / [Sep 08, 2008]
Type Ajax, Java, JSF, Framework
Website www.jboss.org

RichFaces is a rich component library for JavaServer Faces built on the open source framework Ajax4jsf. It allows easy integration of Ajax capabilities into enterprise application development.

RichFaces enriches the Ajax4jsf framework in two ways. First, it expands the number of visual ready-to-use components. Secondly, it implements the skinnability feature of the Ajax4jsf framework including a large number of predefined skins. Using skinnability, it is easier to manage the look-and-feel of an application.

Contents

History of RichFaces

For more details on this topic, see Ajax4jsf.

RichFaces originated from Ajax4jsf framework which was created and designed by Alexander Smirnov.[1] In the fall of 2005, Alexander joined Exadel and continued to develop the framework. The first version of what would become Ajax4jsf was released in March 2006. Later in the same year, Exadel VCP was split off and the Ajax4jsf framework and Rich Faces was born. While RichFaces provided out-of-the-box components or what’s called a component-centric Ajax approach (components do everything you need), Ajax4jsf provided what’s called page-wide Ajax support. You as a developer specify what parts of the page should be processed on server after some client side user actions and what parts should be updated after processing. Ajax4jsf became an open source project hosted on Java.net while RichFaces became a commercial JSF component library.

In March 2007 JBoss (now a division of Red Hat) and Exadel signed a partnership where Ajax4jsf and RichFaces would now be under the JBoss umbrella and be called JBoss Ajax4jsf and JBoss RichFaces. RichFaces would now also be open source and free. In September 2007, JBoss and Exadel decided to merge Ajax4jsf and RichFaces under the RichFaces name. It made sense as both libraries were now free and open source. Having just one product solved many version and compatibility issues that existed before, such as which version of Ajax4jsf works with what version of RichFaces.

Framework

The framework is implemented as a component library which adds Ajax capability into existing pages, so a developer doesn’t need to write any JavaScript code or to replace existing components with new Ajax widgets. RichFaces enables page-wide Ajax support instead of the traditional component-wide support. Hence, a developer can define the event on the page that invokes an Ajax request and the areas of the page that should be synchronized with the JSF Component Tree after the Ajax request changes the data on the server according to the events fired on the client.

RichFaces allows to define (by means of JSF tags) different parts of a JSF page you wish to update with an Ajax request and provide a few options to send Ajax requests to the server. Also JSF page doesn't change from a "regular" JSF page and you don't need to write any JavaScript or XMLHttpRequest objects by hands.

RichFaces architecture

The architecture of RichFaces consists of an Ajax Filter, AJAX Action Components, AJAX Containers, and a JavaScript Engine.

Ajax Filter - In order get all benefits of RichFaces, a developer should register a Filter in web.xml file of the application. The Filter recognizes multiple request types.
AJAX Action Components - AjaxCommandButton, AjaxCommandLink, AjaxPoll and AjaxSupport and other Action Components can be used to send Ajax requests from the client side.
AJAX Containers - AjaxContainer is an interface that describes an area on a JSF page that should be decoded during an Ajax request. AjaxViewRoot and AjaxRegion are implementations of this interface.
JavaScript Engine - RichFaces JavaScript Engine runs on the client-side. It updates different areas on a JSF page based on the information from the Ajax response. JavaScript Engine provides an API so a developer doesn’t need to create own JavaScript functionality.

Skinnability

Skinnability is a special feature of RichFaces that is used for defining common interface styles. The feature is based on XCSS technology which provides flexibility and dynamics. RichFaces provide a set of predefined skins:

  • DEFAULT
  • plain
  • emeraldTown
  • blueSky
  • wine
  • japanCherry
  • ruby
  • classic
  • deepMarine
  • Laguna (new - RichFaces 3.2.1)
  • GlassX (new - RichFaces 3.2.2)
  • DarkX (new - RichFaces 3.2.2)

Skin properties, such as, generalBackgroundColor, generalLinkColor, headerFamilyFont etc are stored in skinname.skin.properties file. Each component has a XCSS (a special file format that combines flexibility of XML and CSS) file that performs mapping of CSS selectors to the skin properties of a particular skin. Additionally, RichFaces provides skinning for standard HTML controls.

Simple JSF page with RichFaces calendar component

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
      xmlns:ui="http://java.sun.com/jsf/facelets"
      xmlns:h="http://java.sun.com/jsf/html"
      xmlns:f="http://java.sun.com/jsf/core"
      xmlns:a4j="http://richfaces.org/a4j"
      xmlns:rich="http://richfaces.org/rich">
  <ui:composition template="/templates/component-sample.xhtml">
    <a4j:outputPanel id="calendar" layout="block">
      <rich:calendar value="#{calendarBean.selectedDate}"
        locale="#{calendarBean.locale}"
        popup="#{calendarBean.popup}"
        datePattern="#{calendarBean.pattern}"
        showApplyButton="#{calendarBean.showApply}"
        cellWidth="24px" cellHeight="22px" style="width:200px"/>                     
    </a4j:outputPanel>
  </ui:composition>
</html>

This is the result of the presented above code:

Image:RichFacesCalendar.png‎

References

  1. ^ Max Katz, Exadel (August 15, 2008). "Ajax4jsf and RichFaces - historical perspective".
Retrieved from "http://en.wikipedia.org/wiki/Richfaces"

No comments have been added.



Your name:

City:

Country:

Your comments:

Security check *
(Please enter the number into adjoining box)