kiwijas.blogg.se

Here’s for example how to prevent your application to use dom4j libraries and use the XOM ( ) object module which we have installed as module name “org.xom”: Īs a footnote, please be aware that you can use the slot parameter in the module name in order to specify a dependency against a particular How to prevent your modules from being loaded using jboss-deployment-structure.xml

However, what if you want to select which packages to use of included itext library? That can be done by defining the itext library as a module and include a filter in it, which excludes for example the com/itextpdf/awt/geom package: Let’s take as an example the following application which is composed of these artifacts: MyApp.earĪs it is, you don’t need configuring the jboss-deployment-structure.xml to use the itext classes, which are picked up from the lib folder. If you need to provide a fine-grained control over your dependencies, you can exclude/include some packages from your dependencies. The above examples are using deployment-based dependencies you can however reference your modules installed in the modules folder as in the following example where we are referencing log4j libraries: If we want a more restrictive policy, we can include the dependency just for the sub-module named myapp.war which is included in the EAR: Here is an example which adds a deployed module to the application’s classpath: An example of jboss-deployment-structure.xml

The advantage of using this file (compared to the Manifest’s entry) is that you can define dependencies across top-level deployments and subdeployments. The file jboss-deployment-structure.xml can ne used to set application dependency against modules.