[
https://issues.redhat.com/browse/WFLY-7395?page=com.atlassian.jira.plugin...
]
Brian Stansberry commented on WFLY-7395:
----------------------------------------
[~ehugonnet] FYI re the above discussion.
I kind of doubt we would do what's requested here. We'd need to add a new API
library for the annotation (unless I've forgotten one that would suit.) It
wouldn't work like @org.jboss.annotation.ejb.Depends which allowed dependencies on
mbean services. In AS > 6 the services we provide and their names are internal details.
So it would have to be something else. Using a JNDI name is possible and then the server
could wire in a dependency on the service backing the binding.
Perhaps the dependency thing could be done, but we'd have to know it actually solves
the complete problem. If there's a different solution that's fine.
Allow to provide deployment dependency to JNDI resource
-------------------------------------------------------
Key: WFLY-7395
URL:
https://issues.redhat.com/browse/WFLY-7395
Project: WildFly
Issue Type: Feature Request
Components: Server
Affects Versions: 10.1.0.Final
Reporter: Miroslav Novak
Assignee: Brian Stansberry
Priority: Major
Labels: user_experience
For JBoss AS 6 there was ejb annotation @org.jboss.annotation.ejb.Depends which allowed
to set dependency to JNDI resource. Currently there seems to be no replacement in Wildfly
10.x
For example if EJB contains dependency to queue registered in JNDI:
{code}
@Resource(mappedName = "java:/jms/queue/OutQueue")
private Queue outQueue;
{code}
then it would not get deployed when OutQueue is not present. Purpose of this feature
request is to add possibility to provide such dependency in the way as
@org.jboss.annotation.ejb.Depends did.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)