geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Donald Woods <>
Subject Re: RELEASE-NOTES-1.1
Date Tue, 13 Jun 2006 19:11:38 GMT
What happens in the case that the files no longer exist on the next 
server startup?  Two scenarios I'm worried about:
1) files were loaded from an NFS/Samba/SMB share which has become 
2) Eclipse users who deploy the app into the server, test it, stop the 
server and then delete the project and files from Eclipse


Aaron Mulder wrote:
> On 6/13/06, Lin Sun <> wrote:
>> I am trying to learn what the in-place deployment mean and how to use it.
>> My understanding was that users can update the hot deploy files (for
>> example, update one jsp file) in the Geronimo_home\deploy directory and
>> server will redeploy the change automatically.   This was not working in
>> 1.0, as users need to replace the entire directory in the
>> Geronimo_home\deploy directory.
> That should be true in both 1.0 and 1.1 (if not, I guess it's a bug).
> But in 1.1, there is a separate option, which is to not copy your
> files to the hot deploy directory at all, but instead use the deploy
> tool with a special option to enable an in-place deployment.  This
> means that instead of copying your files into the server directory at
> all, it will deploy and access them from wherever they currently are.
> Thanks,
>    Aaron
>> But after reading your note below, I think I am lost.   Please advise.
>> Lin
>> -----Original Message-----
>> From: [] On Behalf Of Aaron
>> Mulder
>> Sent: Thursday, June 08, 2006 7:23 PM
>> To:
>> Subject: Re: RELEASE-NOTES-1.1
>>  - We should add a point about in-place deployment.  "Geronimo
>> supports in-place deployment, which means an archive or directory can
>> be deployed without being copied into the Geronimo directory tree."

View raw message