I think that unless you can edit the ears your only solution is to start two different JBoss instances.
But why does everything work fine in the 2.x version and not anymore in the 3.x version?
Is it not possible to configure multiple applications which are somehow separated from each other?
Different classloader architecture.
The new architecture in the default settings, avoids serializations for communication inside JBoss. However, it can cause problems when different versions of a jar/class need to be deployed.
For anyone interested, I found a solution.
In the file: deploy/jbossweb-tomcat41.sar/META-INF/jboss-service.xml
I changed the following tag to false:
I did the same in jboss3.2.3, it doesn't work. Unbelievable, such a product Jboss. This is common J2EE usage: having more ear’s deployed. Any ear’s has its onw classes. Sometimes there are classes in both ears with the same package name, but they can be different or different version. According to J2EE specs about ClassLoding classloaders should first look into war or jar after that in the parent ear. It should not be possible to load classes from a different ears.
I just can’t believe that this is implemented so. This is also security prone. It is against J2EE specs. I will never advise Jboss as application server as long this is not fixed.
Jboss development team, my congratulations !!!
I will never advise Jboss as application server as long this is not fixed. - That should do it, the developers will fix it for you tonight.
If you want to load the classes from that ear alone, scope ur classloader by naming it differently. Lookup the jboss getting started documents on "Scoping Classloaders"