View RSS Feed

JBoss

EAR Class Loading

Rate this Entry
by , 04-27-2012 at 06:33 PM (863 Views)
Ear deployments are multi-module deployments. This means that not all classes inside an ear will necessarily have access to all other classes in the ear, unless explicit dependencies have been defined. By default the EAR/lib directory is a single module, and every WAR or EJB jar deployment is also a separate module. Sub deployments (wars and ejb-jars) always have a dependency on the parent module, which gives them access to classes in EAR/lib, however they do not always have an automatic dependency on each other. This behaviour is controlled via the ear-subdeployments-isolated setting in the ee subsystem configuration:
XML Code:
<subsystem xmlns="urn:jboss:domain:ee:1.0" >            
  <ear-subdeployments-isolated>false</ear-subdeployments-isolated>
</subsystem>
By default this is set to false, which allows the sub-deployments to see classes belonging to other sub-deployments within the .ear.

Submit "EAR Class Loading" to Facebook Submit "EAR Class Loading" to Digg Submit "EAR Class Loading" to del.icio.us Submit "EAR Class Loading" to StumbleUpon Submit "EAR Class Loading" to Google

Categories
JBoss7

Comments