Brian Stansberry [http://community.jboss.org/people/brian.stansberry] created the discussion "Re: Thoughts on filesystem action driven hot deployment" To view the discussion, visit: http://community.jboss.org/message/592847#592847 -------------------------------------------------------------- The foo.war.deployed was a mistake; it's now .isdeployed as we discussed in Antwerp. I told Rob I was going to do that. The deployment-scanner branch has been pushed upstream. So any further work on this will happen from master. The standalone/deployments dir now includes a README.txt with the following content: The standalone/deployments directory in the JBoss Application Server distribution is the location end users can place their deployment content (e.g. war, ear, jar, sar files) to have it automically deployed into the server runtime. Users, particularly those running production systems, are encouraged to use the JBoss AS management APIs to upload and deploy deployment content instead of relying on the deployment scanner subsystem that periodically scans this directory.  See the JBoss AS documentation for details. The filesystem deployment scanner in AS 7 and later works differently from previous JBoss AS releases. The scanner will no longer attempt to directly monitor the deployment content and decide if or when the end user wishes the content to be deployed. Instead, the scanner relies on a system of marker files, with the user's addition or removal of a marker file serving as a sort of command telling the scanner to deploy, undeploy or redeploy content. The marker files always have the same name as the deployment content to which they relate, but with an additional file suffix appended. For example, the marker file to indicate the example.war should be deployed is named example.war.dodeploy. Different marker file suffixes have different meanings. The relevant marker file types are: .dodeploy     -- Placed by the user to indicate that the given content should                  be deployed into the runtime (or redeployed if already                  deployed in the runtime.) .deploying    -- Placed by the deployment scanner service to indicate that it                  has noticed a .dodeploy file and is in the process of                  deploying the content. This marker file will be deleted when                  the deployment process completes. .isdeployed   -- Placed by the deployment scanner service to indicate that the                  given content has been deployed into the runtime. If an end                  user deletes this file, the content will be undeployed. .faileddeploy -- Placed by the deployment scanner service to indicate that the                  given content failed to deploy into the runtime. The content                  of the file will include some information about the cause of                  the failure. .undeploying  -- Placed by the deployment scanner service to indicate that it                  has noticed a .isdeployed file has been deleted and the                  content is being undeployed. This marker file will be deleted                  when the undeployment process completes. .undeployed   -- Placed by the deployment scanner service to indicate that the                  given content has been undeployed from the runtime. If an end                  user deletes this file, it has no impact. Basic workflows: All examples assume variable $AS points to the root of the JBoss AS distribution. A) Add new zipped content and deploy it: 1. cp target/example.war/ $AS/standalone/deployment 2. touch $AS/standalone/deployment/example.war.dodeploy B) Add new unzipped content and deploy it: 1. cp -r target/example.war/ $AS/standalone/deployment 2. touch $AS/standalone/deployment/example.war.dodeploy C) Undeploy currently deployed content: 1. rm $AS/standalone/deployment/example.war.isdeployed D) Replace currently deployed zipped content with a new version and deploy it: 1. cp target/example.war/ $AS/standalone/deployment 2. touch $AS/standalone/deployment/example.war.dodeploy E) Replace currently deployed unzipped content with a new version and deploy    it: 1. rm $AS/standalone/deployment/example.war.isdeployed 2. wait for $AS/standalone/deployment/example.war.undeployed file to appear 3. cp -r target/example.war/ $AS/standalone/deployment 4. touch $AS/standalone/deployment/example.war.dodeploy F) Redeploy currently deployed content (i.e. bounce it with no content    change): 1. touch $AS/standalone/deployment/example.war.dodeploy -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/592847#592847] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]

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 -------------------------------------------------------------- It's all in upstream here: https://github.com/jbossas/jboss-as https://github.com/jbossas/jboss-as 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&...]

Max Rydahl Andersen [http://community.jboss.org/people/maxandersen] created the discussion "Re: Thoughts on filesystem action driven hot deployment" To view the discussion, visit: http://community.jboss.org/message/593001#593001 -------------------------------------------------------------- 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. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/593001#593001] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Max Rydahl Andersen [http://community.jboss.org/people/maxandersen] created the discussion "Re: Thoughts on filesystem action driven hot deployment" To view the discussion, visit: http://community.jboss.org/message/593208#593208 -------------------------------------------------------------- Makes sense concerning .isDeployed; how about the case of users using the management API to undeploy this app - will the marker files get updated too or is that too much magic ;) -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/593208#593208] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Ales Justin [http://community.jboss.org/people/alesj] created the discussion "Re: Thoughts on filesystem action driven hot deployment" To view the discussion, visit: http://community.jboss.org/message/593213#593213 -------------------------------------------------------------- There is no such file, if the foo.jar is exploded. Skywalker:deployments alesj$ pwd /Users/alesj/projects/as7/as/build/target/jboss-7.0.0.Alpha2/standalone/deployments Skywalker:deployments alesj$ ls README.txt foo.jar grapher-web-2.0.0-SNAPSHOT.war grapher-web-2.0.0-SNAPSHOT.war.isdeployed -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/593213#593213] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Max Rydahl Andersen [http://community.jboss.org/people/maxandersen] created the discussion "Re: Thoughts on filesystem action driven hot deployment" To view the discussion, visit: http://community.jboss.org/message/591059#591059 -------------------------------------------------------------- Jason - if AS 7 had hotdeploy by just copying the war/ear/folder there then IDE's would not need to be updated for basic usage. And ant doesn't really need a plugin to utilize this - users just add a <touch name="${deploy.name}.dodeploy"/> to their deployment. Maven is tricky - I guess extending Cargo would be the option to support ? Anyone targeting/working on that ? -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/591059#591059] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]