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 Wed, 14 Jun 2006 18:32:22 GMT
Guess the exception output could be enhanced to include:
  - the module that failed to load (in case you were using the silent 
output option which doesn't list the modules being loaded)
  - clear statement that the server will now be shutdown because of this 
  - hint of how to fix the problem, like editing config.xml

Instead of the current output of -

 >Module 24/24 hello/1.1/war                      Exception in thread 
"main" java.lang.AssertionError: Expected one match for pattern ".", but
got 0 matches
 >        at

I agree that you can't just automatically remove the offending 
application, but maybe a configuration option to "continue on error" 
would be useful while you are developing your app, so you can then 
undeploy or redeploy the offending app...


Gianny Damour wrote:
> Hi Donald,
> There are very good points. How would you expect the server to behave in 
> such scenarios? Currently the server will simply shut-down and, to some 
> extent, I think that this is a safe behaviour.
> Thanks,
> Gianny
> Donald Woods wrote:
>> 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 
>> disconnected
>> 2) Eclipse users who deploy the app into the server, test it, stop the 
>> server and then delete the project and files from Eclipse
>> -Donald
>> 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