1 of 1 people found this helpful
Which MANIFEST.MF did you place the dependency in? If it was in the ear's manifest, you would need to add the keyword "export" after the entry, making it visible to the subcomponents within the ear.
Dependencies: org.quartz export
One other thing -- you mentioned that you placed your module.xml and jar file in modules/org/quartz/main. With WildFly 8, modules were moved into modules/system/layers/base. Have you tried moving your module into modules/system/layers/base/org/quartz/main ?
Thanks for your help! I have a doubt. For JBoss to identify the module and its jar, a jboss-deployment-structure.xml. is mandatory right? Since we are putting this inside the META-INF, will that make any issue, if I deploy the EAR in some other server, like Websphere? (My question is ,can we make this module/jar available to the server some other means independent to the EAR). I am a newbie in WildFly.
Modifying the jboss-deployment-structure.xml is one way to make modules visible to an application, but not the only way. Adding the "Dependencies" MANIFEST entry will achieve the same result. If you add it to the ear's MANIFEST (and export it), the module will become visible to everything in the ear. If you add the entry to a single module within the ear, like a jar file, will make the module visible to only that module. There's also a concept of a "global module", where you can make a change to the standalone.xml, which will make the module visible to all of the applications.