[jboss-jira] [JBoss JIRA] (AS7-6215) Ability to declare a dependency on a service name

Tue Dec 18 21:46:08 EST 2012

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

Stuart Douglas commented on AS7-6215:
-------------------------------------

JNDI services are not always tied to the lifecycle of the underlying component. For example with EJB JNDI binding the component may not have started yet when the JNDI entry is bound. This is necessary for circular references to work correctly, so two EJB's can reference each other via JNDI without causing a circular dependency error. 

> Ability to declare a dependency on a service name
> -------------------------------------------------
>
>                 Key: AS7-6215
>                 URL: https://issues.jboss.org/browse/AS7-6215
>             Project: Application Server 7
>          Issue Type: Feature Request
>    Affects Versions: 7.1.3.Final (EAP)
>            Reporter: Brad Maxwell
>            Assignee: Stuart Douglas
>             Fix For: Open To Community
>
>
> We have several use cases where we need dependencies between different deployments.
> Such as
> Singleton in ear1 which injects an ejb from ear2 using @EJB.  At shutdown we need the Singleton to call a method to clean up on the ejb, however the ejb is sometimes shutdown before the Singleton.  Using @DependsOn would allow the Singleton to depend on the EJB if the EJB is in the same ear as the Singleton, however it is not.
> There are other use cases where resources are injected and we need the resources to still be deployed at shutdown so we can clean up the resources before they are undeployed.
> Having a service name to depend on would be useful and if the name was configurable such that it does not based on the exact name of the deployment, it would be useful as using maven changes the deployment names when we rebuild and we do not want to have to change the code each time we rebuild.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira