Jboss-deployment-structure.xml: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
Line 13: | Line 13: | ||
It must be placed in the <tt>META-INF</tt> or the <tt>WEB-INF</tt> directory of the deployment. | It must be placed in the <tt>META-INF</tt> or the <tt>WEB-INF</tt> directory of the deployment. | ||
It | It can be used for the following: | ||
* | * To prevents [[WildFly Modules#Automatic_Dependencies|automatic dependencies]] from being added. | ||
* To add module dependencies. | |||
* To define additional modules. <font color=red>What for? How is that useful?</font> | |||
* To change an EAR deployments isolated class loading behavior, independently of the general setting described here: [[WildFly Modules#ear-subdeployments-isolated|<tt>ear-subdeployments-isolated</tt> setting]]. | |||
* To add additional resource roots to a module. |
Revision as of 21:16, 10 March 2016
External
- Developer Guide jboss-deployment-structure.xml https://docs.jboss.org/author/display/AS71/Developer+Guide#DeveloperGuide-JBossDeploymentStructureFile
Internal
Overview
jboss-deployment-structure.xml is a WildFly proprietary deployment descriptor that allows finely grained class loading control.
It must be placed in the META-INF or the WEB-INF directory of the deployment.
It can be used for the following:
- To prevents automatic dependencies from being added.
- To add module dependencies.
- To define additional modules. What for? How is that useful?
- To change an EAR deployments isolated class loading behavior, independently of the general setting described here: ear-subdeployments-isolated setting.
- To add additional resource roots to a module.