Writing a Custom WildFly Module: Difference between revisions
Jump to navigation
Jump to search
| Line 16: | Line 16: | ||
==Module Name== | ==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: <tt>com.novaordis.playground.wildfly.custommodule</tt>. | |||
==Module Location== | ==Module Location== | ||
==Module JAR Name== | ==Module JAR Name== | ||
Revision as of 07:50, 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.