geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sachin Patel (JIRA)" <...@geronimo.apache.org>
Subject [jira] Commented: (GERONIMO-686) Directory based hot deployment support
Date Tue, 23 Aug 2005 15:22:09 GMT
    [ http://issues.apache.org/jira/browse/GERONIMO-686?page=comments#action_12319726 ] 

Sachin Patel commented on GERONIMO-686:
---------------------------------------

Does anyone want to work on this and take it over? I submitted this a while back trying to
write a gbean, and I its still on the roadmap for 1.0.  Its been sitting here idle for a while
so this is my attempt to revive it :)  This would be great to have, and I don't think we need
to have anything advance to start of, just some basic means of hot deployment that consumes
prepackaged ears, jars, wars.  I created a simple gbean for this, but ideally it may be better
of to be integrated with one of the existing deployers.  The only other peiece of logic is
the algorithum to monitor a filesystem which I found a open source version of and tweaked
to account for "additions, modifications, and deletions".

This would be a good start for anyone in the community wanting to contribute.  It would be
awesome to take it a step further and be able to drop in individual J2EE artifacts, and have
them automatically be packaged and deployed.

> Directory based hot deployment support
> --------------------------------------
>
>          Key: GERONIMO-686
>          URL: http://issues.apache.org/jira/browse/GERONIMO-686
>      Project: Geronimo
>         Type: New Feature
>     Versions: 1.0-M4
>     Reporter: Sachin Patel
>  Attachments: geronimoautodeploy.zip
>
> Here is an initial start of directory-based hot deployment for Geronimo.  I have not
had the chance to update it with the things I would like to see, so I'm going ahead and submitting
it, so a commiter can tweak it and get it into a build.
> Basically this is a GBean service that monitors a specified directory in the filesystem
for any "additions, modifications, or deletions".  Based on the event, a particual module
in the filesystem will either be deployed, redeployed, or undeployed.  This service takes
the assumtion that the deployment plan is packaged within the module. 
> Also, the specified directory is currently a hard-coded attribute in the deployment plan.
 It would be nice if the configuration started up a webapp as well,and the gbean was linked
to this webapp so that the directory could be changed on the fly, and or multiple directories
as well as other options could be specified.  Perhaps this could be something configurable
in the console?
> Also, I am currently calling the org.apache.geronimo.deployment.Deployer to do the deploy.
 I initially wanted to reference the Deployer gbean and invoke deploy through it, but was
having issues with that, so I used this as a workaround.
> The class that monitors the file sytem I found on the internet, however it was only able
to detected generic changes.  I made modifications to the file so that these changes to the
filesystem are catagorized as either additions, modifiecations, or deletions.  See the license
on the file, as I am unsure weather this can be used or wether it will need to be re-written
from scratch, which if is the case should be trivial.
> Please let me know if this is a good start, any suggestions, and if you think this is
something that can be pushed into 1.0 I will be glad to spend additional time on it to get
it in.  I did this more for a learning exercise so its pretty scrappy right now, but I think
alot could be done with it.
> Thanks!!
> Thanks.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message