Bug 991276 - WAR_BUNDLE_JSF_IMPL does not work inside an EAR
Summary: WAR_BUNDLE_JSF_IMPL does not work inside an EAR
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: JSF
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER2
: EAP 6.2.0
Assignee: Stan Silvert
QA Contact: Marek Schmidt
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-02 04:28 UTC by James Livingston
Modified: 2018-12-06 15:12 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
If a JSF implementation was packaged in a WAR, WAR_BUNDLE_JSF_IMPL could be used to allow it to work rather than the container's implementation. This option was not working if it was instead packaged in an EAR. The cause of this issue was that only the (sub-)deployment was checked for the JSF marker, causing it not to be found when it was in a distinct top-level deployment (EAR). To resolve this issue, an additional check has been implemented to check the top-level deployment for the JSF marker.
Clone Of:
Environment:
Last Closed: 2013-12-15 16:19:50 UTC
Type: Bug
Embargoed:
rdickens: needinfo-

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFLY-1785 0 Minor Resolved WAR_BUNDLES_JSF_IMPL does not work for EAR files 2016-06-13 13:43:07 UTC
Red Hat Knowledge Base (Solution) 466743 0 None None None Never

Description James Livingston 2013-08-02 04:28:50 UTC 
If you package a JSF implementation inside a WAR you can use WAR_BUNDLE_JSF_IMPL to allow it to work rather than the container's implementation.

This does not work if it is packaged into an EAR.
Comment 3 James Livingston 2013-09-05 23:31:45 UTC 
Recreated PR against 6.2, with additional required information.

https://github.com/jbossas/jboss-eap/pull/368
Comment 9 Scott Mumford 2013-11-19 04:13:24 UTC 
Hi Stan.

I was wondering if you'd be able to add some content to 'Doc Text' box above.

I've not been able to determine (from this bug or the linked JIRA/PRs) what was causing the rejection of ear archives nor what action was taken to fix that behaviour.

If you could proved some idea of what caused the problem and how it was fixed, I can draft an entry for the 6.2 Release Notes document.

Thanks
Comment 10 James Livingston 2013-11-19 04:28:45 UTC 
From https://github.com/wildfly/wildfly/commit/5738dcd2a8ddd5bb42582b7078dda5792468540b I'd say:


Cause: Only the (sub-)deployment was checked for the JSF marker, causing it not to be found when it was in a distinct top-level deployment (EAR).

Fix: Check the top-level deployment for the JSF marker.
Note You need to log in before you can comment on or make changes to this bug.