-
2. Re: EAR classloading
attodorov Feb 18, 2007 6:46 AM (in response to attodorov)Hi Jaikiran,
My webapps use a shared utility jar : commons-httpclient-3.0.1.jar. But this is not loaded first. Instead the commons-httpclient.jar is loaded which resides in the JBoss shared lib dirs. As a result i get method signature incompatibilities - i.e. different interfaces, etc. This contradicts with the options:
false
and
false
As you can see, both of them are turned off on my configuration. This is actually the default setting for JBoss 4.0.5.
Is this a bug? Thanks.
Best Regards,
Angel -
3. Re: EAR classloading
attodorov Feb 18, 2007 6:48 AM (in response to attodorov)Hi Jaikiran,
My webapps use a shared utility jar : commons-httpclient-3.0.1.jar. But this is not loaded first. Instead the commons-httpclient.jar is loaded which resides in the JBoss shared lib dirs. As a result i get method signature incompatibilities - i.e. different interfaces, etc. This contradicts with the options:
false
and
false
As you can see, both of them are turned off on my configuration. This is actually the default setting for JBoss 4.0.5.
Is this a bug? Thanks.
Best Regards,
Angel -
4. Re: EAR classloading
jaikiran Feb 18, 2007 2:02 PM (in response to attodorov)Have you configured classloader isolation for your application by specifying
<jboss-app> <loader-repository> com.example:loader=unique-archive-name <loader-repository-config> java2ParentDelegation=false </loader-repository-config> </loader-repository> </jboss-app>
in the jboss-app.xml file of your ear.