Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1122875

Summary: Multi-JSF feature ignore's original modules if custom one is added
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Jonáš Trantina <jtrantin>
Component: JSFAssignee: Farah Juma <fjuma>
Status: CLOSED DUPLICATE QA Contact: Marek Schmidt <maschmid>
Severity: medium Docs Contact: Russell Dickenson <rdickens>
Priority: unspecified    
Version: 6.2.4CC: ssilvert
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-24 13:57:08 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
example cli file to add new JSF module none

Description Jonáš Trantina 2014-07-24 09:29:02 UTC 
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 [1]. 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 [2] is the upstream bug- this seems to be fixed in WildFly but not in Jboss AS 7.

[1] https://community.jboss.org/wiki/DesignOfAS7Multi-JSFFeature
[2] https://issues.jboss.org/browse/WFLY-976


To reproduce:
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.
Comment 1 Jonáš Trantina 2014-07-24 09:33:18 UTC 
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.
Comment 2 Farah Juma 2014-07-24 13:57:08 UTC 
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 ***