geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sachin Patel <sppat...@gmail.com>
Subject Re: The autodeploy feature in Geronimo
Date Mon, 24 Oct 2005 14:16:35 GMT


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.

Wouldn't it be more confusing to the user if their file got removed 
after it got deployed? I feel the point of a "live" directory is for the 
runtime to be able to react to any changes to it, including deletions. 
Both Jboss and Websphere's hot deploy capability allow deletions.

What does tomcat allow?

Sachin

> 
>>
>>>
>>> Jacek
>>>
> 

Mime
View raw message