Difference between revisions of "JBoss JSF Richfaces"
Jump to navigation
Jump to search
Haarlaender (talk | contribs) (New page: =JBoss, JSF and Richfaces= ==JBoss 4.2.2== ===JSF 1.2, Richfaces 3.3.3=== *No problems as JBoss 4.2.x comes with built in JSF 1.2 libraries (Mojarra) *If Facelets are required, use versi...) |
Haarlaender (talk | contribs) |
||
| Line 35: | Line 35: | ||
===JSF 2.0, Richfaces 3.3.3=== | ===JSF 2.0, Richfaces 3.3.3=== | ||
*JBoss 5.1 comes with built in JSF 1.2 libraries | *JBoss 5.1 comes with built in JSF 1.2 libraries | ||
*Two options for update | *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: | ** 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> | <context-param> | ||
| Line 43: | Line 44: | ||
!!!!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. | !!!!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 | ** 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 | ||
Revision as of 15:33, 21 February 2011
JBoss, JSF and Richfaces[edit]
JBoss 4.2.2[edit]
JSF 1.2, Richfaces 3.3.3[edit]
- No problems as JBoss 4.2.x comes with built in JSF 1.2 libraries (Mojarra)
- If Facelets are required, use version 1.15 for compatibility with 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>
JSF 2.0, Richfaces 3.3.3[edit]
- not tested, presumably same as with JBoss 5.1
JSF 2.0, Richfaces 4[edit]
- not tested, presumably same as with JBoss 5.1
JBoss 5.1[edit]
JSF 1.2, Richfaces 3.3.3[edit]
- No problems as JBoss 5.1 comes with built in JSF 1.2 libraries (Mojarra)
- See #JBoss 4.2.2
JSF 2.0, Richfaces 3.3.3[edit]
- 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