geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lin Sun" <linsun....@gmail.com>
Subject RE: RELEASE-NOTES-1.1
Date Tue, 13 Jun 2006 19:25:34 GMT
Good point!  I shutdown the server and renamed the hello directory.  Then
start the server afterwards.  I saw the following exception when server
attempted to start the hello module.  I didn't see Geronimo server started
at the end but luckily all the important module seemed to be started before
my little hello module, which is the last in var\config\config.xml file.

Module 24/24 hello/1.1/war                      Exception in threa
d "main" java.lang.AssertionError: Expected one match for pattern ".", but
got 0
 matches
        at
org.apache.geronimo.kernel.config.ConfigurationUtil.preprocessGBeanDa
ta(ConfigurationUtil.java:331)
        at
org.apache.geronimo.kernel.config.ConfigurationUtil.startConfiguratio
nGBeans(ConfigurationUtil.java:359)
        at
org.apache.geronimo.kernel.config.KernelConfigurationManager.start(Ke
rnelConfigurationManager.java:187)
        at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.startCon
figuration(SimpleConfigurationManager.java:512)
        at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.startCon
figuration(SimpleConfigurationManager.java:493)
        at
org.apache.geronimo.kernel.config.SimpleConfigurationManager$$FastCla
ssByCGLIB$$ce77a924.invoke(<generated>)
        at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java(Inlined
Compil
ed Code))
        at
org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethod
Invoker.java(Compiled Code))
        at
org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperatio
n.java(Inlined Compiled Code))
        at
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.
java(Compiled Code))
        at
org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java(I
nlined Compiled Code))
        at
org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperat
ionInvoker.java(Compiled Code))
        at
org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(Pro
xyMethodInterceptor.java(Compiled Code))
        at
org.apache.geronimo.kernel.config.EditableConfigurationManager$$Enhan
cerByCGLIB$$f05707cd.startConfiguration(<generated>)
        at org.apache.geronimo.system.main.Daemon.doStartup(Daemon.java:297)
        at org.apache.geronimo.system.main.Daemon.<init>(Daemon.java:74)
        at org.apache.geronimo.system.main.Daemon.main(Daemon.java:377)

I guess this error can be improved in the future releases, but for 1.1 user
needs to be good aware of what inPlace means before they use it for 1.1.

I hope this is less of a problem for scenario #2, as I am not aware of the
in-place option to deploy a project in Eclipse/WTP but Sachin can certainly
correct me as I haven't tried the 1.1 version of the Eclipse plugins yet.

Lin

-----Original Message-----
From: Donald Woods [mailto:drw_web@yahoo.com] 
Sent: Tuesday, June 13, 2006 3:12 PM
To: dev@geronimo.apache.org
Subject: Re: RELEASE-NOTES-1.1

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 <linsun.unc@gmail.com> 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: ammulder@gmail.com [mailto:ammulder@gmail.com] On Behalf Of Aaron
>> Mulder
>> Sent: Thursday, June 08, 2006 7:23 PM
>> To: dev@geronimo.apache.org
>> 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."
>>
>>
>>
>>
> 
> 


Mime
View raw message