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

[Max Rydahl Andersen]

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/593368#593368

--------------------------------------------------------------
> Dimitris Andreadis wrote:
> 
> You know, this whole idea with the marker files, I think it's just to complex for a simple deployment. If one is truly interested in deploying in a safe way, they could use the CLI, no?
The CLI does not yet provide a way to do deployments AFAIK and it also requires a running server and seem also to not support exploded/incremental deployemnts - so its for very different usecases.

I'm waiting eagerly to learn how to use the http/native approach to do deployment since that is very useful for remote deployment - but without eploded deployments the file approach is still the best for fast feedback development.

btw. you *always* want to deploy without intermediate scans which was the biggest pain when copying into the server - jboss tools at least made that painless with its disablement of the deployment scanner while copying.


> > > Or, why not turn the problem upside down?
> > > 
> > > Treat the deployments directory exactly like in previous jboss versions (i.e. deploy something when is copied, undeploy when is removed) to retain backwards compatibility with user expectation, tools and the like.
> > > 
> > 
> > 
> > 
> > I would love that and was my initial proposal but was told it could not be done without a lot of overhead/complexity.
> > 
> > 
> > 
> > > In addition, if you want to go for an atomic deployment of XXX (packed or unpacked), create first a marker file XXX.skip, then copy in the deployment (packed or unpacked) and remove the XXX.skip file when done to trigger the deployment. Voila.
> > 
> > 
> > 
> > yup - I think that was called .donotdeploy marker in previous talks.
> > 
> > 
> > 
> > > To undeploy either remove directly the deployment, or if you fear it cannot be done atomically, create again a XXX.skip, remove the deployment and then remove the XXX.skip file to trigger undeployment.
> > 
> > How would adding a .skip befor trying to remove the directory help ?
> > 
> > 
> > 
> > > For a re-deployment just touch the packed file, or the directory in the unpacked case.
> > > 
> > > This would ensure atomic deployments, while retaining "backwards compatibility" for the ./deploy directory notion.
> 
> Yes I agree with this but the state changing files are still superuseful for both tools and users (i.e. .deploying, .deployed, .undeploying, .undeployed) IMO.
--------------------------------------------------------------

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

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/20110315/4b7c35ae/attachment.html