[
https://issues.jboss.org/browse/WFLY-7395?page=com.atlassian.jira.plugin....
]
Miroslav Novak commented on WFLY-7395:
--------------------------------------
[~jmesnil] Hi Jeff, in community forum discussion
(
https://developer.jboss.org/message/964459) user had issue that MDB is activated after
failback before JNDI resources like pooled-connection-factory and queues are present in
JNDI. I guess, this happens because live was syncing journal from backup and until this is
done, live cannot activate and register JNDI resources. In the mean time MDB failed to
deploy and does not get automatically redeployed when live finally activates (failback
completes).
MDB which has dependency to messaging service activates before messaging service is fully
up. Do you think it would be possible to mark messaging service as not up when it's
syncing journal from backup?
Allow to provide deployment dependency to JNDI resource
-------------------------------------------------------
Key: WFLY-7395
URL:
https://issues.jboss.org/browse/WFLY-7395
Project: WildFly
Issue Type: Feature Request
Components: Server
Affects Versions: 10.1.0.Final
Reporter: Miroslav Novak
Assignee: Jason Greene
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.2.3#72005)