> Does this quickstart use Jboss Modules without explicitly define a module in "module" directory of jboss (using module.xml etc.)?
That is right. The quickstart demonstrates how to define dependencies on JBoss modules present in the deployment. Every deployment is treated as a JBoss module, and subarchives within the deployment can also be treated as a module.
Module dependencies are defined via a Dependencies entry in the MANIFEST.MF. This is accomplished via the maven-war-plugin in this example. For more info: https://access.redhat.com/site...
The module names specified in the manifest have to be named in a specific manner, since the referenced modules are present within the deployment and are not supplied by the modules installed into the application server. For more info : https://access.redhat.com/site...
Settings
Vineet Reynolds
> Does this quickstart use Jboss Modules without explicitly define a
module in "module" directory of jboss (using module.xml etc.)?
That is right. The quickstart demonstrates how to define dependencies on JBoss modules present in the deployment. Every deployment is treated as a JBoss module, and subarchives within the deployment can also be treated as a module.
Module dependencies are defined via a Dependencies entry in the MANIFEST.MF. This is accomplished via the maven-war-plugin in this example. For more info: https://access.redhat.com/site...
The module names specified in the manifest have to be named in a specific manner, since the referenced modules are present within the deployment and are not supplied by the modules installed into the application server. For more info : https://access.redhat.com/site...
10:53 a.m., Tuesday Jan. 7
Moderate this comment by email
Email address: vineet.reynolds@gmail.com | IP address: 122.167.103.93
Reply to this email with “Delete”, “Approve”, or “Spam”, or moderate from the Disqus moderation panel.