Re: Static Variables and ClassLoaders

2005-09-13 Thread David Jencks
Hi, That looks to me as if it should work. Do you see the log statements from starting the gbean? If you put log statements in your servlet when it accesses the static instance which occurs first? You might try logging the classloaders involved and their parentIds. thanks david jencks On

Re: Static Variables and ClassLoaders

2005-09-12 Thread Krishnakumar B
Hi, Thanks for the response. I am not sure if i understood ur answer right. I tried the following GBean Plan Config ID = test/Hello http://geronimo.apache.org/xml/ns/deployment"; configId="test/Hello" parentId="org/apache/geronimo/Server" > test/jars/hellogbean.jar

Re: Static Variables and ClassLoaders

2005-09-12 Thread David Jencks
I think you have found the cause of the problems in your other post :-) I'm assuming you are using M5/Head. First, make sure that each jar appears in only one plan as a dependency or as a module in an .ear. Then, locate the plans that contain all the jars you need directly as dependencies or

Static Variables and ClassLoaders

2005-09-12 Thread Krishnakumar B
Hi, I have a doubt related to usage of Static Variables. "Static Variables are scoped in the class they r defined. So if a class is loaded by more than one classloader in same JVM then there will be multiple copies within same JVM" How do i used Config Id/Parent Id to ensure that 2 plans use the