Writing a Custom WildFly Module: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 32: | Line 32: | ||
==Write Code and Package It According the Naming Conventions== | ==Write Code and Package It According the Naming Conventions== | ||
See [[#Naming_Conventions|Naming Conventions]] above. | |||
Revision as of 07:56, 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/
Process
Write Code and Package It According the Naming Conventions
See Naming Conventions above.