Ales Justin [http://community.jboss.org/people/alesj] created the discussion
"Re: Custom Deployer - migrate from JBoss4.2" To view the discussion, visit: http://community.jboss.org/message/588841#588841 -------------------------------------------------------------- > I'm need to determine that given subdeployments is not needed for deployment > at all. In JBoss4 I'm just remove such subdeployments from > DeploymentInfo.subDeployments and all goes OK. > Example deployment structure: > * some-service.myDeployerExt* sub-last.jar > * sub-only-need-in-special-case.jar > * sub-second.jar > * sub-first.jar > > > And I'm need this subdeployments to start in the right order, but > sub-only-need-in-special-case.jar is not need to be started at all: > 1. sub-first.jar > 2. sub-second.jar > 3. sub-last.jar > > Sorting problem I had already solved (thanks a lot!) but how can I exclude > subdeployments from the deployment process at all? I see that task intended > to the StructureDeployer, but can't get a right way... :( Simply use jboss-structure.xml, where you explicitly define (sub)deployments. Or you could add a new StructureDeployer, which would still recognize this sub-deployment, but would mostly make it a no-op; e.g. no classpath, meta locations, ... -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/588841#588841] Start a new discussion in JBoss Microcontainer at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2114]
_______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
