How do I upgrade Mojarra in JBoss server and tell it use the given Mojarra 2.x JARs instead of JBoss own jboss-jsf-api_2.1_spec-2.0.1.Final.jar
as indicated in startup log?
If that's relevant, I am currently using JBoss AS 7.1.
The below procedure applies to JBoss AS 7.2+, JBoss EAP 6.1+, and JBoss WildFly 8+ and assumes that you've full control over the server installation and configuration. This upgrades the server-wide default JSF version:
javax.faces.jar
file). Current latest 2.1.x version is 2.1.29 and current latest 2.2.x version is 2.2.14. Let's assume that you want to upgrade to 2.2.x. You can download them individually from their Maven repository:
/modules/system/layers/base/javax/faces/api/main
:
jsf-api-2.2.14.jar
file in there.module.xml
file and edit <resource-root>
to specify the new file name as in <resource-root path="jsf-api-2.2.14.jar"/>
/modules/system/layers/base/com/sun/jsf-impl/main
:
jsf-impl-2.2.14.jar
file in there.module.xml
file and edit <resource-root>
to specify the new file name as in <resource-root path="jsf-impl-2.2.14.jar"/>
/standalone/data
(except of custom data folders like folder containing uploaded files, of course)/standalone/deployments
/standalone/tmp
The same procedure applies to JBoss AS 7.0/7.1 and JBoss EAP 6.0, you only need to browse in /modules/*
instead of /modules/system/layers/base/*
, and you need to explicitly delete the old .index
file there, if any (JBoss will autocreate one). Also, if the module.xml
in API folder misses <module name="com.sun.jsf-impl"/>
inside <dependencies>
, then you need to manually add it.
Important note is that Mojarra 2.2.x versions older than 2.2.7 will fail in AS/EAP during deployment with the following exception: org.jboss.weld.context.ContextNotActiveException: WELD-001303 No active contexts for scope type javax.faces.flow.builder.FlowDefinition
. You've then basically 2 options: downgrade to Mojarra 2.1.x, or upgrade to at least 2.2.7 or newer.
In case you'd like to upgrade to Mojarra 2.3, which doesn't offer a 2-JAR variant anymore on Maven, you'd need to manually create the 2-JAR variant based on javax.faces.jar
file as per this procedure: How to install one jar variant of JSF (javax.faces.jar) on WildFly.