[
https://issues.jboss.org/browse/WFCORE-1912?page=com.atlassian.jira.plugi...
]
Brian Stansberry commented on WFCORE-1912:
------------------------------------------
I won't reject this because it's a valid request, but I'd be surprised if any
activity happens on it for a long time as it's not clear at all how to do such a
thing. The data structures that record all this dependency state are tied to the objects
that are created as part of deployment and are discarded on undeploy. Keeping all that
data around somehow and then being able to make use of it later would be complex.
I'm not clear though on why the existing rollback-on-runtime-failure=false behavior
doesn't suffice. The behavior at boot is to not roll back. I'll play a bit to see
if I can understand the problem; perhaps some detail has changed that I've forgotten
about.
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
Labels: user_experience
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)