Writing a Custom WildFly Module: Difference between revisions
Jump to navigation
Jump to search
| Line 35: | Line 35: | ||
See [[#Naming_Conventions|Naming Conventions]] above. | See [[#Naming_Conventions|Naming Conventions]] above. | ||
==Copy the JAR under WildFly's | ==Copy the JAR under WildFly's module Directory== | ||
See [[]] above. | See [[#Module_Location|Module Location]] above. | ||
Revision as of 08:00, 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.
Copy the JAR under WildFly's module Directory
See Module Location above.