[
https://issues.jboss.org/browse/WFCORE-2939?page=com.atlassian.jira.plugi...
]
Brian Stansberry edited comment on WFCORE-2939 at 6/8/17 11:16 AM:
-------------------------------------------------------------------
I think the WFCORE-446 work introduced this, by updating the CLI to always send the
'enabled' param to the full-replace-deployment management op. It should only send
it if the user input specifically determines a value; otherwise it should leave it
undefined. If undefined the existing settings on the server-group=x/deployment=y resources
should remain in place.
was (Author: brian.stansberry):
I think the WFCORE-446 work introduced this, by updating the CLI to always send the
'enabled' param to the full-replace-deployment. It should only send it if the user
input specifically determines a value; otherwise it should leave it undefined. If
undefined the existing settings on the server-group=x/deployment=y resources should remain
in place.
Disabled deployments in server group enabled after WAR is updated
-----------------------------------------------------------------
Key: WFCORE-2939
URL:
https://issues.jboss.org/browse/WFCORE-2939
Project: WildFly Core
Issue Type: Bug
Components: CLI, Domain Management
Environment: Centos 7
OpenJDK
Reporter: Matthew Casperson
Updating the contents of a WAR file in a domain controller content repository will
usually lead to a disabled deployment in a server group being enabled.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)