Description of problem:
=======================
If an application which enabled and is targeted to a server group is replaced via console then the replaced application is not by default in Enabled mode. Users need to manually enable it. (in JBoss EAP 6.3 or earlier this behaviour) was different)
How reproducible:
=================
Steps to Reproduce:
- Deploy a simple WAR to "main-server-group" in EAP 6.4
- Access the application and notice that it is enabled properly and accessible.
- Now Via console replace the application with the altered WAR and after replace notice that the application is "Disabled" (where as before Replace it was in active mode, So after replace also it was supposed to be in the same mode)
Actual results:
================
After replace the deployed application was in disabled mode.
Expected results:
================
After replace the deployed application should have been in it's previous state as Enabled mode.
Additional info:
However if we replace the application via jboss-cli.sh script then the application is properly replaced as well as it's state is "Enabled".
Example:
========
[domain@localhost:9999 /] deploy --name=Test.war /PATH/TO/Test.war --force
Description of problem: ======================= If an application which enabled and is targeted to a server group is replaced via console then the replaced application is not by default in Enabled mode. Users need to manually enable it. (in JBoss EAP 6.3 or earlier this behaviour) was different) How reproducible: ================= Steps to Reproduce: - Deploy a simple WAR to "main-server-group" in EAP 6.4 - Access the application and notice that it is enabled properly and accessible. - Now Via console replace the application with the altered WAR and after replace notice that the application is "Disabled" (where as before Replace it was in active mode, So after replace also it was supposed to be in the same mode) Actual results: ================ After replace the deployed application was in disabled mode. Expected results: ================ After replace the deployed application should have been in it's previous state as Enabled mode. Additional info: