You really should not use the java module approach. There are other alternatives. EE5 includes mechanism to load thirdparty jars from a centralized location. In J2EE 1.4 you can declare a libs directory, place your 3rd party jars in them and list each one explicitly in the MANIFEST.MF file of your application components anonymous wrote : | EAR | -->lib | -->jar1 | -->jar2 | ejb-module.jar | -->META-INF | -->MANIFEST.MF | (Class-Path: lib/jar1.jar, lib/jar2.jar | | Note, regular scoping rules apply in that if you are using an isolated CL with Java2ParentDelegation turned off, this will force the load from the lib directory. If not, and a class exists in a higher class loader, this one will be chosen. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3991791#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...