Classpath issue for differant module

Question

If my module uses some version of web service jar file....
and one more module uses upgraded version of web service jar file
all the modules lib files will be placed into single classpath which will break lower version jar file s module.
Is there any way we can differentiate module level classpath with global classpth ?
Sameer
Edited by: sameerdh on Jul 12, 2012 12:07 AM

Answer 1

When you build the ear file, the classpath of is built based on the dependency among modules(set in manifest.mf). So if module A is dependent on B, then in classpath moduleB's jar file will be at the beginning.
But if you still want any of the module classes to take priority , then you can always put those classes in environment variables because system class loader will take priority over any other classloaders ( application/ejb/war class loaders) except bootstrap loader.
Its not recommended to have different versions of classes from each jar file to be executed in jvm, as it would result inconsistency and is prone to various errors. Use one of those versions for your application.
-karthik