[jboss-jira] [JBoss JIRA] (WFCORE-1752) The deployment-overlay command fails to redeploy affected deployments

[ https://issues.jboss.org/browse/WFCORE-1752?page=com.atlassian.jira.plugi... ] Jean-Francois Denise commented on WFCORE-1752: ---------------------------------------------- [~brian.stansberry], [~swd847], I have started to look at how to fix this issue. I am running into issues when dealing with batch mode. Feedback would be welcome. I am trying to keep the --deployments option to reference deployment names and do the conversion to the runtime name internally when needed (mainly when adding the deployment to the overlay). The deployment name seems to me what people are really using to reference deployment (If I am wrong just say it). Furthermore the deployment name is what is needed to do actual redeploy of the deployment (right, no way to do a redeploy using runtime-name?). When a redeploy-affected is required, all the linked deployments being referenced through their runtime-name, we need to retrieve the deployment name in order to redeploy. So this approach hides the runtime-name in all options and output (e.g.: list-link lists the deployment names although overlay contains the runtime-name, so a conversion is operated). This approach seems to work except in the case of batch. In the context of a batch, the deployment could be not already present (being added in a previous step inside the same composite), so there is no way to retrieve what will be the runtime name of it. So we are stuck... If we change the approach and deal with runtime-name instead of name, then we run into a similar issue in batch mode. We need to convert from runtime-name to name in order to do the redeploy. Suggestions welcome. Thanks. JF -- This message was sent by Atlassian JIRA (v7.2.3#72005)