[jboss-dev-forums] [JBoss AS7 Development] - Re: Thoughts on filesystem action driven hot deployment

[jaikiran pai]

jaikiran pai [http://community.jboss.org/people/jaikiran] created the discussion

"Re: Thoughts on filesystem action driven hot deployment"

To view the discussion, visit: http://community.jboss.org/message/594378#594378

--------------------------------------------------------------
> Brian Stansberry wrote:
> 
> Here's what I'm doing. Following uses the term "auto-deploy" to refer to the scanner deciding to deploy without being told to via a .dodeploy marker.
> 
> 1) I'm adding the zip scanning Jason mentioned to detect whether the zip is complete. This is the basis for reliable auto-deploy of zipped content.
> 
> 2) Reliable auto-deploy of exploded content is not possible. As a safety aid I will use the scanning code from 1) to check any nested jars, but that doesn't make it reliable.
> 
> 3) If auto-deploy is available for a type of content, a .skipdeploy marker will prevent auto-deploy of a particular file.
> 
> 3) I'm going to add an "auto-deploy" flag to the deployment-scanner element, with legal values "ALL", "ZIPPED", "NONE". Flag controls what types of content auto-deploy behavior is enabled for. Per Jason's statement above, default is "ZIPPED", as "ALL" cannot be made reliable. Configuring "ALL" will result in a WARN message in the server log.
> 
> 4) For auto-deploy of exploded content, there will be no deployment descriptor file timestamp check as the means of detecting the need to redeploy, as in EE 6 there is no universal requirement for deployment descriptors. And checking the directory timestamp is not valid as it's easy to change content without triggering a change in the directory timestamp. So, with auto-deploy if any file in the deployment changes, the deployment gets redeployed. People who want to change content without triggering redeploy are going to have to use marker files; either leave auto-deploy disabled and use .dodeploy, or enable auto-deploy and use .skipdeploy.
> 
> 5) If a scan tries to use auto-deploy for a file and detects incomplete content, the scan will be aborted (i.e. it will be as if no changes were detected.) The next time the scanner runs, it will check again.
> 
> 
Sounds good!  :)  

One final question:

> 2) Reliable auto-deploy of exploded content is not possible. As a safety aid I will use the scanning code from 1) to check any nested jars, but that doesn't make it reliable.
So triggering a deployment of exploded content (with the auto-deploy flag set to ZIPPED) would require a .dodeploy marker right? I have no issues with using a marker for this specific case - just want to understand the expected behaviour.
--------------------------------------------------------------

Reply to this message by going to Community
[http://community.jboss.org/message/594378#594378]

Start a new discussion in JBoss AS7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2225]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-dev-forums/attachments/20110321/dd48c1b0/attachment.html