Show Table of Contents
3.8. Reference
3.8.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 | Modules Always added | Modules Conditional added | Conditions |
|---|---|---|---|
| Core Server |
|
-
|
-
|
| EE Subsystem |
|
-
|
-
|
| EJB3 subsystem |
-
|
|
The presence of
ejb-jar.xml in valid locations in the deployment, as specified by the Java EE 6 specification or the presence of annotation-based EJBs (e.g. @Stateless, @Stateful, @MessageDriven etc)
|
| JAX-RS (Resteasy) subsystem |
|
| The presence of JAX-RS annotations in the deployment |
| JCA sub-system |
|
| If the deployment is a resource adaptor (RAR) deployment. |
| JPA (Hibernate) subsystem |
|
| The presence of an @PersistenceUnit or @PersistenceContext annotation, or a <persistence-unit-ref> or <persistence-context-ref> in a deployment descriptor. |
| SAR Subsystem |
-
|
| The deployment is a SAR archive |
| Security Subsystem |
|
-
|
-
|
| Web Subsystem |
-
|
| The deployment is a WAR archive. JavaServer Faces(JSF) is only added if used. |
| Web Services Subsystem |
|
-
|
-
|
| Weld (CDI) Subsystem |
-
|
| If a beans.xml file is detected in the deployment |
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.