Hi Lea, I'm using an architecture similar to your GatewayBean except the servlet I use for routing is also deployed to each EAR and only routes to the GatewayBean within that EAR. (My GatewayBean is for EJB client access).
I'm relying on your statement that "each EAR is scoped with its own classloader". In fact, I wasn't aware it was possible (or even desirable) to access a JAR deployed in one EAR from another EAR. I have a utility JAR deployed with each EAR and I'm finding that classes in that JAR are loaded only from the first EAR deployed containing that JAR regardless of the EAR I'm accessing. This seems so arbitrary since it looks as though deployables are processed alphabetically and is especially problematic when I have the need to deploy a specific version of the utility JAR in an EAR. Could this be a bug or maybe a configurable JBoss option? If it is an option, is it the default behavior to allow sharing JARs across EARs and where/how do I change it? BTW - I'm using 3.2.3. Thanks, Mike View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3834257#3834257 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3834257 ------------------------------------------------------- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
