Bug 991276 – WAR_BUNDLE_JSF_IMPL does not work inside an EAR

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 991276 - WAR_BUNDLE_JSF_IMPL does not work inside an EAR

Summary:	WAR_BUNDLE_JSF_IMPL does not work inside an EAR

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	JBoss Enterprise Application Platform 6
Classification:	JBoss
Component:	JSF (Show other bugs)
Sub Component:
Version:	6.1.0
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	ER2
Target Release:	EAP 6.2.0
Assigned To:	Stan Silvert
QA Contact:	Marek Schmidt
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2013-08-02 00:28 EDT by James Livingston
Modified:	2017-10-09 20:23 EDT (History)
CC List:	4 users (show)

See Also:
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 11:19:50 EST
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Flags:	rdickens: needinfo-

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
JBoss Issue Tracker	WFLY-1785	Minor	Resolved	WAR_BUNDLES_JSF_IMPL does not work for EAR files	2016-06-13 09:43 EDT
Red Hat Knowledge Base (Solution)	466743	None	None	None	Never

Groups: None (edit)

Description James Livingston 2013-08-02 00:28:50 EDT

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 19:31:45 EDT

Recreated PR against 6.2, with additional required information.

https://github.com/jbossas/jboss-eap/pull/368

Comment 9 Scott Mumford 2013-11-18 23:13:24 EST

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-18 23:28:45 EST

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.