Back to bug 1029260

Who When What Removed Added
Eiichi Nagai 2013-11-12 01:47:43 UTC Comment 0 is private 1 0
baranowb 2014-07-21 08:55:53 UTC Status NEW ASSIGNED
CC bbaranow
Assignee david.lloyd bbaranow
baranowb 2014-07-21 08:56:12 UTC Summary Cannot use a ear-subdeployments-isolated attribute setting with a jboss-deployment-structure.xml [GSS] (6.4) Cannot use a ear-subdeployments-isolated attribute setting with a jboss-deployment-structure.xml
baranowb 2014-07-21 09:05:37 UTC Docs Contact smumford
QA Contact pslavice
baranowb 2014-07-21 09:32:51 UTC Link ID JBoss Issue Tracker WFLY-3263
baranowb 2014-07-21 09:33:10 UTC Link ID JBoss Issue Tracker WFLY-2569
baranowb 2014-07-22 04:42:46 UTC Status ASSIGNED POST
Kabir Khan 2014-08-28 09:10:52 UTC Target Release --- EAP 6.4.0
CC kkhan
baranowb 2014-08-28 09:35:21 UTC Blocks 1134806
baranowb 2014-08-29 06:59:02 UTC Status POST ASSIGNED
baranowb 2014-08-29 08:19:38 UTC Status ASSIGNED POST
Kabir Khan 2014-08-29 14:44:39 UTC Status POST MODIFIED
Target Milestone --- DR1
Paul Gier 2014-09-16 19:14:56 UTC Status MODIFIED ON_QA
Jan Martiska 2014-09-18 06:59:28 UTC Status ON_QA VERIFIED
CC jmartisk
David Michael 2015-01-22 08:37:20 UTC CC dmichael
Doc Text If you configure a ear-subdeployments-isolated attribute with <filename>jboss-deployment-structure.xml</filename> and put under a <EAR>/META-INF directory, the isolation flag was overwritten by the sub-system configuration.

In JBoss EAP 6.4, this issue is fixed. The order of processing has been updated.
PnT Account Manager 2018-03-06 20:57:01 UTC CC dmichael
Jan Kurik 2019-08-02 07:31:00 UTC Status VERIFIED CLOSED
Resolution --- CURRENTRELEASE
Last Closed 2019-08-02 07:31:00 UTC

Back to bug 1029260