WildFly Modules: Difference between revisions
No edit summary |
No edit summary |
||
| Line 10: | Line 10: | ||
* [[WildFly#Subjects|WildFly]] | * [[WildFly#Subjects|WildFly]] | ||
* [[Java Modules]] | * [[Java Modules]] | ||
=Overview= | |||
A ''WildFly module'' (or JBoss module) is a packaged collection of classes and other resources, along with the specification of what is imported and exported by this module from and to other modules. Each API or service provided by WildFly is implemented as a module, which is loaded or unloaded on demand. | |||
WildFly modules provide finely grained class isolation. They hide server implementation classes from the application and only load the classes the application needs. WildFly modules are peers that remain isolated unless explicitly defined as a dependency of another module. Visibility rules have sensible defaults and can be customized. | |||
=Organizatorium= | |||
Upon the first ''use'' of the module, JBoss creates a <module-name>.jar.index file <font color=red>containing a list of packages? directories? .... </font>. | |||
Revision as of 07:26, 19 January 2016
External
- JBoss Modules Documentation (old) https://docs.jboss.org/author/display/MODULES/Home
- Binaries https://repository.jboss.org/nexus/content/repositories/releases/org/jboss/modules/jboss-modules/
- JIRA https://issues.jboss.org/projects/MODULES
- Layered Distributions and Module Path Organization by Brian Stansberry https://developer.jboss.org/wiki/LayeredDistributionsAndModulePathOrganization
Internal
Overview
A WildFly module (or JBoss module) is a packaged collection of classes and other resources, along with the specification of what is imported and exported by this module from and to other modules. Each API or service provided by WildFly is implemented as a module, which is loaded or unloaded on demand.
WildFly modules provide finely grained class isolation. They hide server implementation classes from the application and only load the classes the application needs. WildFly modules are peers that remain isolated unless explicitly defined as a dependency of another module. Visibility rules have sensible defaults and can be customized.
Organizatorium
Upon the first use of the module, JBoss creates a <module-name>.jar.index file containing a list of packages? directories? .... .