Emanuel Muckenhuber [
http://community.jboss.org/people/emuckenhuber] created the
discussion
"Re: Thoughts on filesystem action driven hot deployment"
To view the discussion, visit:
http://community.jboss.org/message/592996#592996
--------------------------------------------------------------
Max Rydahl Andersen wrote:
Thanks for the writeup Brian, which git repo contains these fixes ?
It's all in
upstream here:
https://github.com/jbossas/jboss-as https://github.com/jbossas/jboss-as
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.
--------------------------------------------------------------
Reply to this message by going to Community
[
http://community.jboss.org/message/592996#592996]
Start a new discussion in JBoss AS7 Development at Community
[
http://community.jboss.org/choose-container!input.jspa?contentType=1&...]