JBoss JSF 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:

org.richfaces.ui richfaces-ui 3.3.3.Final org.richfaces.framework richfaces-impl 3.3.3.Final

com.sun.facelets jsf-facelets 1.1.15
 * If Facelets are required, use version 1.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

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: Following instructions on:

JSF libraries (jsf-api.jar & jsf-impl.jar, jboss-faces.jar and jboss-mc-int-servlet.jar from JBoss 6) must be included in WEB-INF/lib directory of the war file. Additionally, the following lines must be set in web.xml:  org.jboss.jbossfaces.WAR_BUNDLES_JSF_IMPL true</param-value> </context-param> <context-param> com.sun.faces.injectionProvider</param-name> <param-value>org.jboss.web.jsf.integration.injection.JBossInjectionProvider</param-value> </context-param>

INFO [config] Initializing Mojarra (1.2_12-b01-FCS) for context '/digi_lifecycle'
 * JBoss still logs version 1.2 at startup, but anyway JSF 2 seems to run


 * 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 here as it is.
 * This page suggests to also replace the jboss-faces.jar: - Doesn't work for me strange ClassNotFoundExceptions occur

SEVERE [compiler] Error Loading Library: vfszip:/C:/jboss/jboss-5.1.0.GA.JSF2/server/default/deploy/jbossweb.sar/jsf-libs/jsf-impl.jar/com/sun/faces/metadata/taglib/composite.taglib.xml
 * New Expression Language functionality (paramters in method calls etc.)cannot be used with both configs (with&without modifications of JBoss).
 * Another Problem: Errors like the following occur, but they do not seem to bother the application

Richfaces 3.3.3
org.richfaces.ui</groupId> richfaces-ui</artifactId> 3.3.3.Final org.richfaces.framework</groupId> richfaces-impl-jsf2</artifactId> 3.3.3.Final
 * 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:
 * Mojarra 2.0.2 or 2.0.3. should be used. With 2.0.4, an view-handler error occurs.

<context-param> javax.faces.DISABLE_FACELET_JSF_VIEWHANDLER</param-name> <param-value>true</param-value> </context-param>
 * 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:

com.sun.facelets</groupId> jsf-facelets</artifactId> 1.1.15
 * If Facelets is required, version 1.1.15 has to be used.

<view-handler> com.sun.facelets.FaceletViewHandler </view-handler>
 * ... and must be explicitely activated in faces-config:

Richfaces 4.0

 * Richfaces 4.0 is fully compatible with JSF 2
 * Currently, only milestone release is available, which still seems to be quite incomplete.
 * Richfaces 4.0 Release Plan says that final version will be available March 2011
 * Many changes in names from version 3.3.3, no ready documentation yet.

=JBoss 6.0=

JSF 1.2

 * Not of interest

JSF 2

 * JBoss 6 comes with built-in JSF 2 libraries
 * Full support of new Expression Language and Java EE 6 specification

Richfaces 3.3.3

 * Same problems with facelets compatibility as described for
 * However: No error messages occur here if facelets 1.1.15 is used

Richfaces 4

 * Works fine, but currently no final version provided (see )