-
Enhancement
-
Resolution: Won't Do
-
Major
-
None
-
None
-
None
Currently to configure a different JSF Implementation in a module, these steps below are followed:
1. $ mkdir -p modules/com/sun/jsf-impl/JSF_IMPL_NAME-JSF_VERSION
2. Copy the wildfly-jsf-injection and weld-core-jsf JAR files from EAP_HOME/modules/system/layers/base/org/jboss/as/jsf-injection/main/ to the modules/com/sun/jsf-impl/JSF_IMPL_NAME-JSF_VERSION/ subdirectory.
For initial setup, the jars that need to be copied may be from modules/system/layers/base/org/jboss/as/jsf-injection/main or if an Update is applied, then it should be from the latest dir of the form system/layers/base/.overlays/layer-base-jboss-eap-7.2.z.CP/org/jboss/as/jsf-injection/main
After a new Update, if a bug gets fixed in the jars, then the user needs to copy the updated jars into their custom module.
It would be better if the user can just create a module with their jars and depend on the org/jboss/as/jsf-injection module and then the JSF subsystem make it work.
- is related to
-
WFLY-12666 JPA jipijapa use optional dependencies instead of modifying the system module
- Closed
- relates to
-
JBEAP-17861 [GSS](7.3.z) Clarify where from copy wildfly-jsf-injection and weld-core-jsf jar files in patched server
- Closed