The servlet spec calls for isolated classloading. So by default, Web apps in JBoss do not share the same classloading cache as EJBs do. You'll have to modify this file:
and change to the following values:
Yes, the documentation on JBoss classloading is a bit esoteric.
Sorry, it cut out my XML. Here are the values you need to set.
<attribute name="Java2ClassLoadingCompliance">true</attribute> <attribute name="UseJBossWebLoader">true</attribute>
Well, partly solved. It was a Tomcat class loading methodology issue.
The change below did the trick for me with the exception of loading order. The scheduler is still loading before my classes
Thanks to: Javid Jamae
In file: [JBoss]/server/[configuration]/jboss-tomcat55.sar/META-INF/jboss-service.xml
Add or change these attributes to true:
I'm not sure which scheduler you are talking about, but you could try to use the PrefixedDeploymentSorter setting on the URLDeploymentScanner in the following file:
Just use a numeric prefix on your application.
Or, using the regular deployment sorter you can put ".last" on your application to make sure that it is deployed last.