[
https://issues.jboss.org/browse/WFCORE-1912?page=com.atlassian.jira.plugi...
]
Miroslav Novak commented on WFCORE-1912:
----------------------------------------
Can this be set on deployment and not on deploy operation? The issue which was discussed
in forum is that server boots and starts deploy of MDB with @Resource dependency to queue.
Deployment fails because queue is not deployed yet. Queue gets deployed later (for example
after Artemis live server activates after failback and deploys all its JNDI resources like
queues and connection factories to JNDI) and MDB notices it and automatically redeploys.
Redeploy deployment if all missing dependencies for deployment are
corrected
-----------------------------------------------------------------------------
Key: WFCORE-1912
URL:
https://issues.jboss.org/browse/WFCORE-1912
Project: WildFly Core
Issue Type: Enhancement
Components: Server
Reporter: Miroslav Novak
Assignee: Jason Greene
If deployment failed to deploy and later all missing dependencies for deployment are
corrected then deployment would redeploy automatically. This behavior could be
configurable.
For example if you deploy EJB which injects queue like:
{code}
@Resource(mappedName = "java:/jms/queue/OutQueue")
private Queue outQueue;
{code}
and administrator deploys queue later then EJB would automatically get redeployed.
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)