Bug 1029260 - [GSS] (6.4) Cannot use a ear-subdeployments-isolated attribute setting with a jboss-deployment-structure.xml
Summary: [GSS] (6.4) Cannot use a ear-subdeployments-isolated attribute setting with a...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: EE
Version: 6.1.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: DR1
: EAP 6.4.0
Assignee: baranowb
QA Contact: Pavel Slavicek
Scott Mumford
URL:
Whiteboard:
Depends On:
Blocks: 1134806
TreeView+ depends on / blocked
 
Reported: 2013-11-12 01:47 UTC by Eiichi Nagai
Modified: 2019-08-02 07:31 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
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.
Clone Of:
: 1134806 (view as bug list)
Environment:
Last Closed: 2019-08-02 07:31:00 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFLY-2569 0 Major Closed Components in Web and EJB container should always have access to RAR included in the same EAR 2018-05-28 17:03:51 UTC
Red Hat Issue Tracker WFLY-3263 0 Major Closed ear-sub-deployments-isolated is ignored from jboss-deployment-structure.xml 2018-05-28 17:03:50 UTC

Description Eiichi Nagai 2013-11-12 01:47:25 UTC
Created attachment 822734 [details]
simple reproducer

Description of problem:
Even if configure a ear-subdeployments-isolated attribute with jboss-deployment-structure.xml [1] and put under a <EAR>/META-INF directory, the isolation flag will be overwritten by the sub-system configuration [2].

[1] jboss-deployment-structure.xml
<jboss-deployment-structure>
<ear-subdeployments-isolated>true</ear-subdeployments-isolated>
</jboss-deployment-structure>

[2] org.jboss.as.ee.component.deployers.DefaultEarSubDeploymentsIsolationProcessor.java
53#    @Override
54#    public void deploy(DeploymentPhaseContext phaseContext) throws DeploymentUnitProcessingException {
55#        final DeploymentUnit deploymentUnit = phaseContext.getDeploymentUnit();
56#        // we only process .ear
57#        if (!DeploymentTypeMarker.isType(DeploymentType.EAR, deploymentUnit)) {
58#            return;
59#        }
60#        final ModuleSpecification moduleSpecification = deploymentUnit.getAttachment(Attachments.MODULE_SPECIFICATION);
61#        // set the default ear subdeployment isolation value
-> 62#        moduleSpecification.setSubDeploymentModulesIsolated(earSubDeploymentsIsolated);
63#    }


Version-Release number of selected component (if applicable):
6.1.1
6.2.0 Beta1 (AS 7.3.0.Final-redhat-8)

How reproducible:
Always

Steps to Reproduce:
1. Run EAP 6 server (using a standalone.sh)
2. Depoloy a SimpleEAR.ear (This application sets a ear-subdeployments-isolated=true with META-INF/jboss-deployment-structure.xml).

Actual results:
3. You can deploy it.

Expected results:
4. Stop EAP 6 server.
5. Modify a standalone.xml
- Add following.

        <subsystem xmlns="urn:jboss:domain:ee:1.1">
            <ear-subdeployments-isolated>true</ear-subdeployments-isolated>

6. Run EAP 6 server (using a standalone.sh)
7. You cannot deploy the SimpleEAR.ear for NoClassDefFoundError or ClassNotFoundException.

I think that the result of Step 3 must be the same as this.

Comment 4 Jan Martiska 2014-09-18 06:59:28 UTC
Verified in EAP 6.4.0.DR1.1.


Note You need to log in before you can comment on or make changes to this bug.