How to install one jar variant of JSF 2.3 (javax.faces.jar) on WildFly

by

Here’s the manual procedure:

  1. Extract javax.faces.jar with a ZIP tool. You’ll get 3 folders com, javax, META-INF
    (NOTE: in some versions you’ll also see a jsf.js file in the root, but this is a mistake, you should ignore it, it’s already located in META-INF/resources/javax.faces)

  2. Pack com and META-INF folders into jsf-impl.jar with a ZIP tool.

  3. Then, delete all files/subfolders in META-INF except of MANIFEST.MF.

  4. Pack javax and META-INF folders into jsf-api.jar with a ZIP tool.

  5. Continue here with those JARs: Upgrade JSF / Mojarra in JBoss AS / EAP / WildFly.

For the interested, JBoss AS and WildFly has internally a modular separation of Java EE based API and impl files. The separated JAR files jsf-api.jar and jsf-impl.jar are still needed. The reason is not really technical, but just an extra service to force developers programming against the right libraries. Only the API modules are exposed during compile time (usually, via the IDE-integrated plugin which adds them to “build path”). This should avoid starters accidentally finding, importing and using implementation classes such as those in com.sun.faces.* package.

Already since version 1.x, the JSF implementation Mojarra was composed of two JAR files: jsf-api.jar and jsf-impl.jar. The API JAR contained the javax.faces.* classes and the implementation JAR contained the com.sun.faces.* classes. Since the change of the build system conform Java EE Maven rules, both the API and implementation classes were merged into a single javax.faces.jar file, see also issue 2028 (started with Mojarra 2.1.6 at Dec 2011). Since Mojarra 2.3, the separated JAR files are not built anymore.

More Related Contents:

  1. Upgrade JSF / Mojarra in JBoss AS / EAP / WildFly
  2. Changing faces-config.xml from 2.2 to 2.3 causes javax.el.PropertyNotFoundException: Target Unreachable, identifier ‘bean’ resolved to null
  3. commandButton/commandLink/ajax action/listener method not invoked or input value not set/updated
  4. Understanding PrimeFaces process/update and JSF f:ajax execute/render attributes
  5. How to include another XHTML in XHTML using JSF 2.0 Facelets?
  6. Why do I need to nest a component with rendered=”#{some}” in another component when I want to ajax-update it?
  7. How do I process GET query string URL parameters in backing bean on page load?
  8. JSTL c:if doesn’t work inside a JSF h:dataTable
  9. ViewParam vs @ManagedProperty(value = “#{param.id}”)
  10. Is it suggested to use h:outputText for everything?
  11. Defining and reusing an EL variable in JSF page
  12. Accessing injected dependency in managed bean constructor causes NullPointerException
  13. File upload doesn’t work with AJAX in PrimeFaces 4.0/JSF 2.2.x – javax.servlet.ServletException: The request content-type is not a multipart/form-data
  14. Maven and JSF webapp structure, where exactly to put JSF resources
  15. Hit a bean method and redirect on a GET request
  16. Find component by ID in JSF
  17. How and when is a @ViewScoped bean destroyed in JSF?
  18. How to bind dynamic content using ?
  19. Difference between rendered and visible attributes of
  20. How to add placeholder attribute to JSF input component?
  21. How to create a composite component for a datatable column?
  22. Unable to find matching navigation case with from-view-id ‘/pages/index.xhtml’
  23. How do I force an application-scoped bean to instantiate at application startup?
  24. Open new window by POST using h:commandButton
  25. How to concatenate Strings in EL expression?
  26. Read resource bundle properties in a managed bean
  27. What jsf component can render a div tag?
  28. How to escape f:selectItem itemLabel attribute
  29. Is Facelets page generated to Servlet as JSP generated to Servlet
  30. Skip required validation and invoke the application

Leave a Comment