WildFly Class Loading: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 21: Line 21:
WildFly adds module dependencies for a JEE deployment in a very specific order, starting from the highest priority to the lowest priority:
WildFly adds module dependencies for a JEE deployment in a very specific order, starting from the highest priority to the lowest priority:
# '''System Dependencies''' - these are the dependencies that are automatically added by the container. For more details see [[WildFly Modules#Automatic_Dependencies|automatic dependencies]].
# '''System Dependencies''' - these are the dependencies that are automatically added by the container. For more details see [[WildFly Modules#Automatic_Dependencies|automatic dependencies]].
# ''User Dependencies'' - these are the dependencies that are added through <tt>[[jboss-deployment-structure.xml]]</tt>, through the <tt>Dependencies:</tt> manifest entry for modules or through <tt>Class-Path:</tt> for JAR files.
# '''User Dependencies''' - these are the dependencies that are added through <tt>[[jboss-deployment-structure.xml]]</tt>, through the <tt>Dependencies:</tt> manifest entry for modules or through <tt>Class-Path:</tt> for JAR files.
# '''Local Resources''' - class files packaged inside the deployment itself (example, classes from <tt>WEB-INF/classes</tt> or <tt>WEB-INF/lib</tt> in a WAR file.
# ''Inter-Deployment Dependencies''' - dependencies on other deployments in an EAR deployment. This can include classes in an EAR's <tt>lib</tt> directory or classes defined in other EJB JARs.

Revision as of 20:25, 10 March 2016




Migrating from https://home.feodorov.com:9443/wiki/Wiki.jsp?page=JBoss7ClassLoading


External

Internal

Overview

WildFly class loading relies on modules that have to define explicit dependencies on other modules. This model is different from the previous EAP 5 hierarchical class loading model.

Class Loading Precedence

WildFly adds module dependencies for a JEE deployment in a very specific order, starting from the highest priority to the lowest priority:

  1. System Dependencies - these are the dependencies that are automatically added by the container. For more details see automatic dependencies.
  2. User Dependencies - these are the dependencies that are added through jboss-deployment-structure.xml, through the Dependencies: manifest entry for modules or through Class-Path: for JAR files.
  3. Local Resources - class files packaged inside the deployment itself (example, classes from WEB-INF/classes or WEB-INF/lib in a WAR file.
  4. Inter-Deployment Dependencies' - dependencies on other deployments in an EAR deployment. This can include classes in an EAR's lib directory or classes defined in other EJB JARs.