[jboss-jira] [JBoss JIRA] (AS7-3148) Allow dependency configuration for deployment scanner

[Brian Stansberry (JIRA)]

    [ https://issues.jboss.org/browse/AS7-3148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12663197#comment-12663197 ] 

Brian Stansberry commented on AS7-3148:
---------------------------------------

at javax.naming.InitialContext.lookup(InitialContext.java:392) [:1.6.0_30]
at com.britensw.pluto.web.seam.ManagedPersistenceContext.getEntityManagerFactoryFromJndiOrValueBinding(ManagedPersistenceContext.java:186) 

There is no guarantee of a dependency relationship between deployments when programmatic lookups like this are used. If you use EE injection or EE deployment descriptors, when the deployments are processed the relationships are detected and appropriate service dependencies are created. But the deployers have no visibility to this kind of programatic lookup.

See https://docs.jboss.org/author/display/AS71/Class+Loading+in+AS7 for information on how to declare dependencies between deployments.

BTW, if you are controlling this stuff with scripts, why not have the scripts control the CLI? You can get a lot more control over the behavior of the CLI than you can over the scanner.
                
> Allow dependency configuration for deployment scanner
> -----------------------------------------------------
>
>                 Key: AS7-3148
>                 URL: https://issues.jboss.org/browse/AS7-3148
>             Project: Application Server 7
>          Issue Type: Feature Request
>    Affects Versions: 7.1.0.CR1
>         Environment: AS7.1.0.Final-SNAPSHOT in standalone using standalone-ha.xml
>            Reporter: Brent Douglas
>         Attachments: deployment-scanner.log
>
>
> It would be really handy to be able to specify dependencies for the deployment scanner to abide by. E.g. I have an application with the following structure:
> {code}
> A.ear
> |-B.jar
> \-C.war
> D.war
> {code}
> If D has a dependency on B and they are deployed at the same time I'll get:
> JBAS014775:    New missing/unsatisfied dependencies:
>       service jboss.module.spec.service."deployment.A.ear".main (missing) dependants: [service jboss.module.service."deployment.D.war".main, service jboss.deployment.unit."D.war".POST_MODULE]
>       service jboss.module.spec.service."deployment.A.ear.B.jar".main (missing) dependants: [service jboss.module.service."deployment.D.war".main, service jboss.deployment.unit."D.war".POST_MODULE]
> It would be great though if I could specify that I don't want to deploy D until A is deployed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira