Deployable Modules ?

[rkite01]

    Is there a way to make modules deployable so that JBoss does not have to be restarted when they are compiled?  Where would the module.xml reside?  META-INF directory?

[alesj]

You mean modules in modules/ dir?

They are not hot deployable, but you can add new any time - as they are only looked on-demand.

Otoh, each app is a deployable module -- see previous posts for the actual module name.

[rkite01]

  Can a module be included in a jar and dropped in the deployments directory?  Thus hot deployed.

[alesj]

A jar in deployment/ *is* a module. Just dunno how much you can control resource visibility.

[rkite01]

  I am having a hard time getting 2 ears to see some of my common code libraries/jars.  I really do not want to make them a static modules since they are being modified a lot.   In JBoss 4.2.3 this was not a problem.  The common jars were loaded in I guess a common classloader from my main ear file.  Other ears automatically had visiblity to the common code libraries deployed in the initial ear.     

[kabirkhan]

You can add a Dependencies entry to the including ear's manifest.mf as mentioned in https://docs.jboss.org/author/display/AS7/Class+Loading+in+AS7.

Or if you want more control you can add a jboss-deployment-structure.xml

[rkite01]

I can successfully reference the top level jar in my ear buy using deployment.myear.ear.topjar.jar in Manifest.MF of war.   I still do not know how to reference the jars in the ear/lib directory from the external war.  Is there something that needs to be configured to expose them or maybe I am using the wrong path to the lib?   I tried several paths but none worked.