Jboss-deployment-structure.xml: Difference between revisions

From NovaOrdis Knowledge Base
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 controls the following:
It can be used for the following:
* Prevents [[WildFly Modules#Automatic_Dependencies|automatic dependencies]] from being added.
* To prevents [[WildFly Modules#Automatic_Dependencies|automatic dependencies]] from being added.
Add additional dependencies
* To add module dependencies.
Define additional modules  
* To define additional modules. <font color=red>What for? How is that useful?</font>
Change an EAR deployments isolated class loading behaviour
* 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]].
Add additional resource roots to a module
* To add additional resource roots to a module.

Revision as of 21:16, 10 March 2016

External

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.