]
Brian Stansberry commented on WFLY-13322:
-----------------------------------------
IMO any further enhancement related to installing a different JSF impl should involve a
Galleon feature pack.
^^^ is a very hand-wavy statement but generally our provisioning strategy should be
Galleon.
Ability to configure JSF Implementation that uses the jsf-injection
module instead of copying jars
--------------------------------------------------------------------------------------------------
Key: WFLY-13322
URL:
https://issues.redhat.com/browse/WFLY-13322
Project: WildFly
Issue Type: Enhancement
Components: JSF
Reporter: Brad Maxwell
Assignee: Farah Juma
Priority: Major
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.