this question was already answered - the answer is by setting the configuration inside
the tomcat bundle web.xml not to use jboss loading but the regular one
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3835815#3835815
Reply to the post :
http://www.jboss.o
Set the UseJBossWebLoader to false in jbossweb-tomcat41.sar/META-INF/jboss-service.xml
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3835831#3835831
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3835831
-
Hello? No way to have different classloaders for war's inside an ear ? :/
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3835827#3835827
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3835827
---
I just read the other thread next to me... and it says that truely only the root
deployment can set the loader repository, but does that means all my wars are stuck
with the same loader repository?! isnt it against the j2ee spec for seperation of
loaders for each WEB-INF of each war?
View the o
