[
https://issues.jboss.org/browse/WFCORE-1577?page=com.atlassian.jira.plugi...
]
Brian Stansberry commented on WFCORE-1577:
------------------------------------------
The problem is in DeploymentHandlerUtil.undeploy, which is written as if it is only called
from an op targeting a deployment resource, but DeploymentFullReplaceHandler invokes it
from the root resource. It takes the resource at the op address and removes all the
subsystem children.
This fails if neither the server-group/deployment add op nor the full-replace-deployment
op have the "enabled" param defined, or if the former has it defined as
"true" and the latter as "false". Those are the combinations that
result in DeploymentHandlerUtil.undeploy being invoked.
After a full-replace-deployment operation a server on a hosts
subsystem model is empty
--------------------------------------------------------------------------------------
Key: WFCORE-1577
URL:
https://issues.jboss.org/browse/WFCORE-1577
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Reporter: James Perkins
Assignee: Brian Stansberry
Priority: Blocker
Attachments: WFCORE-1577-test-case.patch
Executing a {{full-replace-deployment}} operation on a deployment deployed to a server in
a managed domain will result a servers subsystem model to be an empty list.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)