I deployed two similar ear-files on JBoss 4.0.0RC2. Those ear have the following content:
test1.ear:
common.jar
entity.jar
session.jar
webservice1.war
test2.ear:
common.jar
entity.jar
session.jar
webservice2.war
common contains some utility classes, entity.jar all entity-bean stuff, session.jar the SLSBs and webservice?.war the webservice-classes,-interfaces and -config-files.
The webservices are deployed es servlets with different context-roots.
I want to use the structure above to deploy a prod- and test-version of our application on one jboss-server.
When the deployment process has finished, the webservices are accessible over the different URL's, but only the latest deployed JSE is called.
So if test is deployed last and I can call the prod-WS via prod-URL, the test-WS is executed and data access and modification is done in the test database.
I've already created an jboss-app.xml with a unique loader-repository entry to get the ears loaded in different classloaders.
But it didn't solve my problem.
