Created attachment 920485 [details]
example cli file to add new JSF module
Description of problem:
When a custom JSF module is added as described here . The original modules (1.2 and main) are no longer available, only the newly added module is available.
The availability of JSF modules is checked via CLI: "/subsystem=jsf:list-active-jsf-impls".
I believe WFLY-976  is the upstream bug- this seems to be fixed in WildFly but not in Jboss AS 7.
Run the .cli file attached to the case- this adds mojarra 2.2. Restart the server and run "/subsystem=jsf:list-active-jsf-impls" -> only the newly added module is available, both 1.2 and main is no longer there.
The workaround is to copy the original modules from modules/system/layers/base/ to modules/ (that is where the new JSF module is added).
It seems that if a module is found in modules/ then modules/system/layers/base/ is no longer scanned.
This issue duplicates bug 1054051. This has been fixed in EAP 6.3.0.
*** This bug has been marked as a duplicate of bug 1054051 ***