JBoss JSF Richfaces

JBoss, JSF and Richfaces

JBoss 4.2.2

JSF 1.2

• No problems as JBoss 4.2.x comes with built in JSF 1.2 libraries (Mojarra)

Richfaces 3.3.3

Required Dependencies:

<dependency>
  <groupId>org.richfaces.ui</groupId>
  <artifactId>richfaces-ui</artifactId>
  <version>3.3.3.Final</version>
</dependency>

<dependency>
  <groupId>org.richfaces.framework</groupId>
  <artifactId>richfaces-impl</artifactId>
  <version>3.3.3.Final</version>
</dependency>

• If Facelets are required, use version 1.15 for compatibility with RichFaces 3.3.3

JSF 2.0

• not tested, presumably same as with JBoss 5.1

JBoss 5.1

JSF 1.2

• No problems as JBoss 5.1 comes with built in JSF 1.2 libraries (Mojarra)
• See #JBoss 4.2.2

JSF 2.0

• JBoss 5.1 comes with built in JSF 1.2 libraries
• Two options for update to JSF 2.0:

• • Without modification of JBoss libraries: JSF libraries (jsf-api.jar & jsf-impl. jar) must be included in WEB-INF/lib directory of the war file. Additionally, the following line must be set in web.xml:

<context-param>
 <param-name>org.jboss.jbossfaces.WAR_BUNDLES_JSF_IMPL</param-name>
 <param-value>true</param-value>
</context-param>

!!!!Beware: The name of the JSF jar files must be exactly the same as in the JBoss deploy directory. This leads to a problem with Maven, which automatically adds the version number to the files.

• • With modification of JBoss: Replace the two JSF libraries (jsf-api.jar & jsf-impl. jar) in /server/default/deploy/jbossweb.sar/jsf-libs with the ones of version 2. Beware that they must have the same filename. Leave jboss-faces.jar as it is.

• New Expression Language functionality (paramters in method calls etc.)cannot be used!

Richfaces 3.3.3

• Richfaces 3.3.3.Final is partly JSF 2 compatible
• Seperate richfaces-impl JSF 2 library is available, ui library stays the same as for JSF 1.2:

<dependency>

  <groupId>org.richfaces.ui</groupId>
  <artifactId>richfaces-ui</artifactId>
  <version>3.3.3.Final</version>
</dependency>

<dependency>
  <groupId>org.richfaces.framework</groupId>
  <artifactId>richfaces-impl-jsf2</artifactId>
  <version>3.3.3.Final</version>
</dependency>

• Richfaces 3.3.3.Final is not compatible with Facelets 2, which is included in JSF 2 libraries. Thus, it has to be deactivated in web.xml:

<context-param>
  <param-name>javax.faces.DISABLE_FACELET_JSF_VIEWHANDLER</param-name>
  <param-value>true</param-value>
</context-param>

• If Facelets is required, version 1.1.15 has to be used..

<dependency>
  <groupId>com.sun.facelets</groupId>
  <artifactId>jsf-facelets</artifactId>
  <version>1.1.15</version>
</dependency>	

• ... and must be explicitely activated in faces-config:

<application>    
  <view-handler>
   com.sun.facelets.FaceletViewHandler
  </view-handler>
</application>

Open source Java EE-based application server

JavaServer Faces