Only JBoss 4.x is J2EE 1.4 compliant. JBoss 3.2.x is J2EE 1.3 compliant. EAR isolation can be achived by a modification of .../conf/jboss-service.xml
.... .... .... <mbean code="org.jboss.deployment.EARDeployer" name="jboss.j2ee:service=EARDeployer"> <!-- Isolate all ears in their own classloader space --> <attribute name="Isolated">true</attribute> <!-- Enforce call by value to all remote interfaces --> <attribute name="CallByValue">true</attribute> </mbean> .... ....
Thank you, I am aware of these details (and many more... I participated in many discussions and tests on the topic over the last year). The problem is that full 100% isolation (not just between ears but even between the ears jBoss itself) is very hard to achieve and perhaps not yet fully possible on jBoss (i.e.: unwanted interactions of libraries like log4j, commons, etc.).
jBoss has made great improvements in this area but I don't think there is a version of jBoss (and corresponding configuration instructions "that work") to fully achieve it. Which is why I suggest the "100% J2EE 1.4 compliant" configuration in addition to the current ones for future versions... simply to reduce the massive pain that is deploying "portable applications" on jBoss.