geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bobby Abraham <>
Subject Re: The autodeploy feature in Geronimo
Date Sun, 23 Oct 2005 23:18:01 GMT
On Sun, 2005-10-23 at 16:00 -0600, Jeff Genender wrote:
> Sachin Patel wrote:
> > 
> > 
> > Jacek Laskowski wrote:
> > 
> >  Am I right that the simplest solution is to develop a GBean that
> > 
> >> would monitor a directory and hand over a deployable to a deployer?
> > 
> > 
> > This was my thinking as well.  The directory would listen for adds, 
> > modifications, and deletions.
> I think this may be somewhat confusing.  I think when dropping in the 
> directory, it should should deploy...then be immediately removed from 
> the directory.  IMHO, this dir should be for hot deploy only.  Let the 
> deployer decide if it should be updated or added.  I think the deletions 
> should not be done through this dir.  We should use the normal undeploy 
> capabilities of the deployer.

As a user it would be nice if a copy to the hot-deploy directory had the
effect of an undeploy of any existing application of the same name and
then reployment of the new one.  This is the most common use case within

It is also very common for the copy to the hot-deploy directory to be
over a slower network.  When this happens it is important to check that
the file is not still being written and avoid deploying an application
before the copy is complete.

There is also the issue of deploying with a separate plan.  In this case
I suggest copying the plan first and ignoring it until the application
is copied, then use the plan for the hot deployment and finally remove
both the plan and the application from the hot-deploy directory. 

- bobby

Bobby Abraham <>
Subtle Guru

View raw message