[
https://issues.jboss.org/browse/JBAS-9057?page=com.atlassian.jira.plugin....
]
John Bailey commented on JBAS-9057:
-----------------------------------
This is an issue. The problem is at server start the actual standalone.xml configuration
is used to determine what is deployed. So just removing the war would not remove it from
the servers repository. We really need to handle the case where the .isdeployed is
missing at server boot and process it as an undeploy.
Can't undeploy on startup
-------------------------
Key: JBAS-9057
URL:
https://issues.jboss.org/browse/JBAS-9057
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 7.0.0.Beta1
Reporter: Stan Silvert
Fix For: 7.0.0.Beta2
1) Deploy a WAR with a *.dodeploy file.
2) Stop the server
3) Remove the *.isDeployed file
4) Restart the server
WAR is still deployed. I expect it to undeploy since isDeployed is now removed.
At this point, the only way I see to undeploy it is to create another dodeploy file, let
it deploy again, and then delete isDeployed while the server is running.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira