VITHUN VENGOPALAN wrote:
I couldn't quite understand the warning that was given at the end of that section,
The ear-subdeployments-isolated element value has no effect on the isolated classloader of the .war file(s). i.e. irrespective of whether this flag is set to true or false, the .war within a .ear will have a isolated classloader and other sub-deployments within that .ear will not be able to access classes from that .war. This is as per spec.
It means that - If you have .ear with a.jar (let's assume it's a EJB deployment) and b.war and b.war contains foo.bar class, then that class will not be accessible from the a.jar classes.