Upgrade JSF / Mojarra in JBoss AS / EAP / WildFly

by

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:

  • Download the individual Mojarra API and impl files (and thus not the single 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:
  • Make sure that JBoss is shutdown.
  • Update JSF API in /modules/system/layers/base/javax/faces/api/main:
    • Delete or backup the old JAR file (do NOT keep it in the same folder, even not renamed!).
    • Put jsf-api-2.2.14.jar file in there.
    • Open module.xml file and edit <resource-root> to specify the new file name as in <resource-root path="jsf-api-2.2.14.jar"/>
  • Update JSF impl in /modules/system/layers/base/com/sun/jsf-impl/main:
    • Delete or backup the old JAR file (do NOT keep it in the same folder, even not renamed!).
    • Put jsf-impl-2.2.14.jar file in there.
    • Open module.xml file and edit <resource-root> to specify the new file name as in <resource-root path="jsf-impl-2.2.14.jar"/>
  • Cleanup JBoss cache/work data just to make sure that there’s no old copy of the JARs from previous deployments hanging in there which would potentially only collide with the new JARs:
    • Trash all contents of /standalone/data (except of custom data folders like folder containing uploaded files, of course)
    • Trash all contents of /standalone/deployments
    • Trash all contents of /standalone/tmp
  • Start JBoss. It should now use the new JSF version for all deployments.

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.

More Related Contents:

  1. com.sun.faces.numberOfViewsInSession vs com.sun.faces.numberOfLogicalViews
  2. What is the usefulness of statelessness in JSF?
  3. Difference between Mojarra and MyFaces
  4. How to update Mojarra version in GlassFish
  5. Running JSF 2.0 on Servlet 2.4 container
  6. Configuration of com.sun.faces.config.ConfigureListener
  7. commandButton/commandLink/ajax action/listener method not invoked or input value not set/updated
  8. How to include another XHTML in XHTML using JSF 2.0 Facelets?
  9. How to reference CSS / JS / image resource in Facelets template?
  10. How can I pass selected row to commandLink inside dataTable or ui:repeat?
  11. Why do I need to nest a component with rendered=”#{some}” in another component when I want to ajax-update it?
  12. When to use f:viewAction / preRenderView versus PostConstruct?
  13. How do I process GET query string URL parameters in backing bean on page load?
  14. Obtaining Facelets templates/files from an external filesystem or database
  15. Difference between View and Request scope in managed beans
  16. What’s the view build time?
  17. Bean Validation @NotNull, @NotBlank and @NotEmpty does not work in JSF+Tomcat
  18. What is the use of faces-config.xml in JSF 2?
  19. Avoiding duplicate ids when reusing facelets compositions in the same naming container
  20. How to implement a dynamic list with a JSF 2.0 Composite Component?
  21. PrimeFaces validator not fired
  22. How to handle session expiration and ViewExpiredException in JSF 2?
  23. How does JSF 2 ConversationScope work?
  24. Creating FacesMessage in action method outside JSF conversion/validation mechanism?
  25. JSF does not populate @Named @RequestScoped bean with submitted input values
  26. Initialization of List in a JSF Managed bean
  27. java.lang.IllegalStateException at com.sun.faces.context.FacesContextImpl.assertNotReleased
  28. How to escape f:selectItem itemLabel attribute
  29. JSF: Mojarra vs. OmniFaces @ViewScoped: @PreDestroy called but bean can’t be garbage collected
  30. How to use Parameterized MessageFormat with non-Value attributes of JSF components

Leave a Comment