]
Thomas Diesler updated WFLY-117:
--------------------------------
Comment: was deleted
(was: Done)
Add and deploy does not fail if runtimeName already exists
----------------------------------------------------------
Key: WFLY-117
URL:
https://issues.jboss.org/browse/WFLY-117
Project: WildFly
Issue Type: Bug
Components: OSGi, Server
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: 8.0.0.Alpha1
The ServerDeploymentHelper has this code
{code}
public String deploy(String runtimeName, InputStream input) throws
ServerDeploymentException {
ServerDeploymentActionResult actionResult;
try {
DeploymentPlanBuilder builder = deploymentManager.newDeploymentPlan();
builder = builder.add(runtimeName, input).andDeploy();
DeploymentPlan plan = builder.build();
DeploymentAction action = builder.getLastAction();
Future<ServerDeploymentPlanResult> future =
deploymentManager.execute(plan);
ServerDeploymentPlanResult planResult = future.get();
actionResult = planResult.getDeploymentActionResult(action.getId());
} catch (Exception ex) {
throw new ServerDeploymentException(ex);
}
if (actionResult.getDeploymentException() != null)
throw new ServerDeploymentException(actionResult);
return runtimeName;
}
{code}
which does not fail if the runtimeName already exists
There is a debug log like this
{code}
11:11:25,103 DEBUG [org.jboss.as.controller.management-operation] (pool-4-thread-1)
JBAS014616: Operation ("add") failed - address: ([("deployment" =>
"v200.jar")]) - failure description: "JBAS014803: Duplicate resource
[(\"deployment\" => \"v200.jar\")]"
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: