[jboss-jira] [JBoss JIRA] (WFCORE-776) handleDeployment() not called for each sub-deployment
Brandon Gaisford (JIRA)
issues at jboss.org
Tue Jun 23 12:18:03 EDT 2015
[ https://issues.jboss.org/browse/WFCORE-776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13082961#comment-13082961 ]
Brandon Gaisford commented on WFCORE-776:
-----------------------------------------
You can close this issue as invalid. I added some additional logging to SubDeploymentProcessor and DeploymentStructureDescriptorParser and was able to verify that everything is working as expected. Given that this deployment activity is executing concurrently on multiple "MSC service thread"/s, I was missing events while debugging through my IDE. This concurrent execution also accounts for the "random" appearance of which wars I was seeing being processed via handleDeployment(...).
Apologies for the confusion.
> 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)
More information about the jboss-jira
mailing list