WildFly Class Loading: Difference between revisions
Jump to navigation
Jump to search
Migrating from https://home.feodorov.com:9443/wiki/Wiki.jsp?page=JBoss7ClassLoading
No edit summary |
|||
| Line 20: | Line 20: | ||
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. | |||
Revision as of 20:23, 10 March 2016
External
- Class Loading in AS7 https://docs.jboss.org/author/display/AS7/Class+Loading+in+AS7
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:
- System Dependencies - these are the dependencies that are automatically added by the container. For more details see automatic dependencies.
- 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.