Writing a Custom WildFly Module: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 34: Line 34:


See [[#Naming_Conventions|Naming Conventions]] above.
See [[#Naming_Conventions|Naming Conventions]] above.
==Copy the JAR under WildFly's <tt>module</tt> Directory==
See [[]] above.

Revision as of 07:59, 19 January 2016

External

Internal

Example


https://github.com/NovaOrdis/playground/tree/master/wildfly/custom-module

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 [[]] above.