此内容没有您所选择的语言版本。
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.
	
| 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  
					 ejb-jar.xml file within a valid location in the deployment, as described in the Java EE 6 specification.
					
						The presence of annotation-based EJBs, for example:  
					 @Stateless, @Stateful, @MessageDriven
					 | 
| 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  
					 @PersistenceUnit or @PersistenceContext annotation, or a <persistence-unit-ref> or <persistence-context-ref> element in a deployment descriptor.
					
						JBoss EAP 6 maps persistence provider names to module names. If you name a specific provider in the  
					 persistence.xml file, a dependency is added for the appropriate module. If this not the desired behavior, you can exclude it using a jboss-deployment-structure.xml file.
					 | 
| Logging subsystem |  
  |   |   
						These dependencies are always added unless the  
					 add-logging-api-dependencies attribute is set to false.
					 | 
| 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 |  
  |   |   | 
| Weld (CDI) Subsystem |   |  
  |  The presence of a beans.xml file in the deployment.  |