Show Table of Contents
3.9.1. Implicit Module Dependencies
The following table lists the modules that are automatically added to deployments as dependencies and the conditions that trigger the dependency.
Table 3.1. Implicit Module Dependencies
|Subsystem Responsible for Adding the Dependency||Dependencies That Are Always Added||Dependencies That Are Conditionally Added||Conditions That Trigger the Addition of the Dependency|
|Core Server|| || || |
|EE subsystem|| || || |
|EJB 3 subsystem|| || || |
The presence of an
The presence of annotation-based EJBs, for example:
|JAX-RS (RESTEasy) subsystem|| || ||The presence of JAX-RS annotations in the deployment.|
|JCA subsystem|| || ||The deployment of a resource adapter (RAR) archive.|
|JPA (Hibernate) subsystem|| || || |
The presence of an
JBoss EAP 6 maps persistence provider names to module names. If you name a specific provider in the
|Logging subsystem|| || || |
These dependencies are always added unless the
|SAR subsystem|| || ||The deployment of a SAR archive.|
|Security subsystem|| || || |
|Web subsystem|| || ||The deployment of a WAR archive. JavaServer Faces (JSF) is added only if it is used.|
|Web Services subsystem|| || || |
If it is not application client type, then it will add the conditional dependencies
|Weld (CDI) Subsystem|| || || The presence of a |
|Container Managed Persistence (CMP) Subsystem|| || |
3.9.2. Included Modules
A table listing the JBoss EAP 6 included modules and whether they are supported can be found on the Customer Portal at https://access.redhat.com/articles/1122333.
3.9.3. JBoss Deployment Structure Deployment Descriptor Reference
The key tasks that can be performed using this deployment descriptor are:
- Defining explicit module dependencies.
- Preventing specific implicit dependencies from loading.
- Defining additional modules from the resources of that deployment.
- Changing the subdeployment isolation behavior in that EAR deployment.
- Adding additional resource roots to a module in an EAR.