Writing a Custom WildFly Module: Difference between revisions
Jump to navigation
Jump to search
| Line 18: | Line 18: | ||
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: <tt>com.novaordis.playground.wildfly.custommodule</tt>. | 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: <tt>com.novaordis.playground.wildfly.custommodule</tt>. | ||
==Module JAR Name== | |||
Conventionally, it should be the condensed form of the module name, including the version string. Example <tt>custom-wildfly-module-1.0.jar</tt>. | |||
==Module Location== | ==Module Location== | ||
| Line 24: | Line 28: | ||
$JBOSS_HOME/modules/com/novaordis/playground/wildfly/custommodule/<version>|main/ | $JBOSS_HOME/modules/com/novaordis/playground/wildfly/custommodule/<version>|main/ | ||
</pre> | </pre> | ||
Revision as of 07:53, 19 January 2016
External
- How to create custom Modules in JBoss EAP 6 https://access.redhat.com/solutions/195403
Internal
Example
Naming Conventions
Module Name
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.
Module JAR Name
Conventionally, it should be the condensed form of the module name, including the version string. Example custom-wildfly-module-1.0.jar.
Module Location
$JBOSS_HOME/modules/com/novaordis/playground/wildfly/custommodule/<version>|main/