3.7. Class Loading and Subdeployments
3.7.1. Modules and Class Loading in Enterprise Archives
- The contents of the
lib/directory in the root of the EAR archive is a module. This is called the parent module.
- Each WAR and EJB JAR subdeployment is a module. These modules have the same behavior as any other module as well as implicit dependencies on the parent module.
- Subdeployments have implicit dependencies on the parent module and any other non-WAR subdeployments.
Class-Path entries in the
MANIFEST.MF file of each subdeployment.
3.7.2. Subdeployment Class Loader Isolation
3.7.3. Enable Subdeployment Class Loader Isolation Within a EAR
Add the deployment descriptor fileAdd the
jboss-deployment-structure.xmldeployment descriptor file to the
META-INFdirectory of the EAR if it doesn't already exist and add the following content:
<ear-subdeployments-isolated>element to the
jboss-deployment-structure.xmlfile if it doesn't already exist with the content of
Subdeployment class loader isolation will now be enabled for this EAR deployment. This means that the subdeployments of the EAR will not have automatic dependencies on each of the non-WAR subdeployments.