Bug 991276

Summary:	WAR_BUNDLE_JSF_IMPL does not work inside an EAR
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	James Livingston <jlivings>
Component:	JSF	Assignee:	Stan Silvert <ssilvert>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Marek Schmidt <maschmid>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.1.0	CC:	joallen, jsenshar, smumford, ssilvert
Target Milestone:	ER2	Flags:	rdickens: needinfo-
Target Release:	EAP 6.2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
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.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-12-15 16:19:50 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:

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.