[jboss-jira] [JBoss JIRA] (WFCORE-776) handleDeployment() not called for each sub-deployment

[Brandon Gaisford (JIRA)]

     [ https://issues.jboss.org/browse/WFCORE-776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brandon Gaisford updated WFCORE-776:
------------------------------------
    Summary: handleDeployment() not called for each sub-deployment  (was: handleDeployment() not called for each subdeployment)


> handleDeployment() not called for each sub-deployment
> -----------------------------------------------------
>
>                 Key: WFCORE-776
>                 URL: https://issues.jboss.org/browse/WFCORE-776
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Server
>    Affects Versions: 2.0.0.Alpha5
>            Reporter: Brandon Gaisford
>            Assignee: Jason Greene
>         Attachments: test-ear.ear
>
>
> When deploying an ear (test-ear.ear) with included jboss-deployment-structure.xml as shown below:
> <jboss-deployment-structure>
>     <deployment>
>         <exclusions>
>             <module name="org.hibernate" slot="main" />
>         </exclusions>
>         <dependencies>
>             <module name="org.apache.log4j" />
>         </dependencies>
>     </deployment>
>     <sub-deployment name="test-war.war">
>     	<exclusions>
>             <module name="org.jdom" slot="main" />
>         </exclusions>
>     	<dependencies>
>     		<module name="org.apache.commons.collections" />	
>     	</dependencies>
>     </sub-deployment>
>     <sub-deployment name="test-war2.war">
>     	<dependencies>
>     		<module name="org.apache.commons.collections" />	
>     	</dependencies>
>     </sub-deployment>
> </jboss-deployment-structure>
> DeploymentStructureDescriptorParser.handleDeployment(...) only gets called for the ear deployment and for one of the war sub-deployments.  The war sub-deployment that does get processed appears to be random.  I would expect handleDeployment(...) to get called for the ear and each war.
> I discovered this issue while working on WFCORE-648.   



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)