Max Rydahl Andersen wrote:
A few questions come up with me trying these things out a bit (based on the previous as7 builds on hudson)
I've had AS7 go bad on me because of some bugs in the deployer, so bad that I couldn't startup thus I removed both the .war.deployed and .war files to trigger the undeployment....but it seem to not have an effect - it still deployed what was in the standalone.xml - I guess because it doesn't retain enough state to decide how to undeploy based on filemarkers?
This might be expected behavior, but its a bit confusing ;)
Would you expect that putting .war.undeploy before AS7 starts up would work ?
That's the expected behavior currently. When starting up AS we first try to restore the persisted state and then check for deployment modifications. However failed deployments should get rolled back and not be persisted in standalone.xml.
okey - so keeping a foo.war.undeploy in the deployment folder at startup should trigger undeploy - but only after it tried deploying the state of the standalone.xml ?
The problem is that sometime deployments work fine from the perspective of AS7 but some runtime issue triggers problems and thus one would like to ensure its not getting deployed - but I guess the only option is then to manually edit the xml file...since using the remote API would have the same problems.