1 Reply Latest reply on Feb 6, 2012 5:06 AM by jaikiran pai

    AS 7 EAR Classloading

    VITHUN VENGOPALAN Newbie

      In JBOSS AS 7 Developer Guide > Class loading in AS 7 > EAR Class Loading section, its mentioned that with ear-subdeployments-isolated option set as false, EJB's and WAR's can cross refer each other without any explicit dependency mapping.

       

      I tried to run a sample application and it didn't throw any dependency issue.

       

      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.

        • 1. Re: AS 7 EAR Classloading
          jaikiran pai Master

          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.