Jboss-deployment-structure.xml; module.xml; Overview. A WildFly module (or JBoss module) is a packaged collection of classes and other resources, along with the specification of what is imported and exported by this module from/to other modules. Each API or service provided by WildFly is implemented as a module, which is loaded or unloaded on.
- https://github.com/NovaOrdis/playground/tree/master/jboss/wildfly/custom-module
The module name is a dot-separated, fully qualified, unique, package name-like string. Conventionally, the name of the module coincides with the embedded top package, though nothing bad seems to happen it does not. Example: com.novaordis.playground.wildfly.custommodule.
Conventionally, it should be the condensed form of the module name, including the version string. Example custom-wildfly-module-1.0.jar.
See Naming Conventions above.
See Module Location above.
The content of the module.xml should be similar to:
- Expressing Module Dependencies in module.xml
In case of a web application, place a jboss-deployment-structure.xml similar to the example shown below under WEB-INF:
Create the EAP module as artifact of a dedicated 'eap-module' Maven module:
- Deploying a Module with CLI