This content has been marked as final.
Show 5 replies
-
1. Re: Classloading in 3.2.3
juha Dec 12, 2003 1:10 PM (in response to gwwallace)Try changing the UseJBossWebLoader attribute to false in your tomcat service META-INF. This should revert back to the prior "half-integrated" web loader behavior. Assuming you're loading something from a WAR this might be the cause.
-
2. Re: Classloading in 3.2.3
gwwallace Dec 12, 2003 2:32 PM (in response to gwwallace)I am using the prefix loader, so I load an ear first,
then load a sar last.
I want the code that is within the sar to be able to access resources in the ear. -
3. Re: Classloading in 3.2.3
juha Dec 12, 2003 2:44 PM (in response to gwwallace)Where is the resource located exactly inside the EAR?
-
4. Re: Classloading in 3.2.3
gwwallace Dec 12, 2003 3:07 PM (in response to gwwallace)its in the toplevel, ie same level as META-INF
-
5. Re: Classloading in 3.2.3
timm Feb 27, 2004 10:04 AM (in response to gwwallace)"juha@jboss.org" wrote:
Try changing the UseJBossWebLoader attribute to false in your tomcat service META-INF. This should revert back to the prior "half-integrated" web loader behavior. Assuming you're loading something from a WAR this might be the cause.
Thanks a lot!
Setting this attribute to false fixed our problem:
>>
our two web Turbine 2.3 applications are running fine in JBoss 3.2.1.
In JBoss 3.2.3 (jboss-3.2.3 &tomcat-4.1.29) web application that has been deployed first functions properly. The second one not.
These two applications has the same set of jar files under WEB-INF/lib.
>>