Brian Wallis wrote:

I don't think it is consistent either. If I have two jars test1.jar and test2.jar where test1.jar has a Class-Path: test2.jar then

- if test1 is deployed first I get two class loaders for test2

- if test2 is deployed first I get only one class loader for test2,
  when test1 is loaded it sees that test2 is already available and
  doesn't re-load it.

(I've done this with both 3.0.7 and 3.2.1)
There are still two class loaders, but the classes from test2 may have been loaded into the ULR cache such that it is irrelevant that test1.jar references test2.jar.


As it is I'll have to stop using Class-Path in Manifests. Pity, it seemed a reasonable way to specify dependencies between jar files.


brian...

It would be except that the URLClassLoader addes Class-Path references to its classpath and effectively causes duplication of classes. We will probably have to write our own replacement in the future to deal with this and other undesirable behavior.

--
xxxxxxxxxxxxxxxxxxxxxxxx
Scott Stark
Chief Technology Officer
JBoss Group, LLC
xxxxxxxxxxxxxxxxxxxxxxxx



-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
same time. Free trial click here: http://www.vmware.com/wl/offer/345/0
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to