How do I handle class version dependencies in different jar files?

[zekela104]

Hi:

I created a new system module x for an external jar file, x.jar, I was given. The external jar file contains an older version of org.mozilla.javascript.

My application war file contains an internal jar file, y.jar, in ./WEB-INF/lib. The internal jar file contains a newer version of org.mozilla.javascript. My application war file also contains another internal jar file, z.jar, which depends on the newer version of org.mozilla.javascript from y.jar.

At runtime, when z.jar attempts to use org.mozilla.javascript, the older version of org.mozilla.javascript in x.jar is used and the request fails with a NoSuchMethodException exception.

At build time, how do I specify that the newer version of org.mozilla.javascript in y.jar should be used rather than the older version from x.jar?

Thank you and sincerely,

Steve

[nickarls]

Not quite sure I'm following but if the "system module" with x.jar is a JBoss Modules module it shouldn't be picked up in the first place unless the dependency has been explicitly stated in the application, or?

[zekela104]

in ./META-INF/MANIFEST.MF, i have

Manifest-Version: 1.0

Dependencies: x

[nickarls]

Hmm. Not sure. You might want to see if jboss-structure.xml can give you any option. JBoss Modules probably has some versioning support, too. Although I'm still not quite getting the picture why you declare the dependency to the module if you don't want stuff picked up by the application...

[zekela104]

I have to declare the module dependency because it's needed functionally by my application. The issue is that inside of the module, which is a "native" jar file from WebLogic (i.e. wlfullclient.jar) are several top-level package hierarchies, including org.mozilla.javascript. As this is a native jar file, I cannot opine as to why it includes mozilla classes. Another part of my application is BIRT. It is completely unrelated to the WebLogic functionality. When the BIRT reporting engine is created by the application, it too needs to use org.mozilla.javascript. But, instead of picking it up from js.jar, which is found in ./WEB-INF/lib/js.jar, it finds it in wlfullclient.jar. But the version of org.mozilla.javascript needed by BIRT is newer than the one found in wlfullclient.jar and my application fails at runtime with a NoSuchMethodException. I am looking for a way to specify that org.mozilla.javascript is to be found in js.jar from my application war rather than from the system module wlfullclient.jar

[nickarls]

OK, now I think I understand the problem at least ;-)

Wonder if the filtering feature of jboss-deployment-structure.xml mentioned in https://docs.jboss.org/author/display/AS71/Class+Loading+in+AS7 could be used for stripping out the mozilla stuff from wlfullclient.jar in import?

[zekela104]

Thanks for the advice, Nicklas. I will take a look at it.