[
https://issues.jboss.org/browse/AS7-6215?page=com.atlassian.jira.plugin.s...
]
Brad Maxwell commented on AS7-6215:
-----------------------------------
I like the JNDI name approach, it would be easy to understand and customers would already
be looking at the JNDI names when using @Resource or @EJB. It would also abstract away
from using deployment names which many have had issues with as they deploy with version
numbers on their deployments.
There is another use case I've seen though it didn't make as much sense, but
customer wanted an ejb to depend on a Servlet - needing the servlet init to have been
called to setup something. I suppose we could just require for that use case that the
servlet bind something into jndi when it is done.
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