Bug 1232061

Description of problem:
Domain mode: To make new version app can be used without restarting server, CLI can do it with command "deploy xx.war --force"(xx.war is the new version app which didn't change its file name)
But in web management console, it became inconvenient and may be a bug in it.

Version-Release number of selected component (if applicable):
Red Hat JBoss Enterprise Application Platform 6.4.0

How reproducible:
It can be reproduced easily.

Steps to Reproduce:
1. Deploy "test.war" on EAP 6.4, make sure its "index.jsp" can be visited.
1. In IDE, change some words in "index.jsp" from app and export it as "test.war" file.
2. Go to EAP 6.4.0's web management console--> Deployments--> ContentRepository --> select "test.war" from list and click "Replace" button --> select the latest "test.war" click "open", "Next" and "Save".
3. Go to "SERVER GOURPS" Tab--> select the server-group which has deployed "test.war" before -->"view"
4. You will find "test.war"'s status is "disabled", click "En/Disable" button, then "test.war" became "enabled", BUT no messages printed in log and refresh "index.jsp" didn't show the changes, you have to click "En/Disable" twice to make it work.
5. Refreshing "index.jsp" to see the changed words.

Actual results:
Click "En/Disable" button 3 times to re-deploy app.

Expected results:
Click "En/Disable" button 1 time to re-deploy app.

Additional info:
We have another way to do that:
1. remove "test.war" from server-groups.
2. replace "test.war" from Content Repository.
3. Assign "test.war" to server-groups.
4. refresh "index.jsp", the update words can be seen.
Please let us know if it is a bug?  If not what is the right way to achieve it?