> On 2003-07-16 06:32 Scott M Stark <[EMAIL PROTECTED]> wrote:
>
> Yes, one for the Class-Path which associates the jar with the referencing 
> deployment and one since its a stand alone deployment.

This seems odd behaviour. It will cause duplicate class loaders for jars and 
hence illegal type problems. It seems to me that this makes Class-Path in the 
manifest dangerous to use.

> Every deployment has its own class loader. Think of hot deployment. Read the 
> class loader docs available on sourceforge docs section for more details.

I am a documentation subscriber and have read that section of the 3.0.7 manual 
and some of the references. Perhaps I need to read it again.

I am not in disagreement with each deployment having it's own classloader, but 
in this case with a Class-Path you get two classloaders for one deployment. 
There should not be duplicates of classes in separate deployment archives, 
but just because one archive references another via a Class-Path declaration 
doesn't really require that it have an extra class loader. 

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)

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...

>> On Wed, 16 Jul 2003 15:58, Brian Wallis wrote:
>> 
>>>This seems to result in ojdbc14 being loaded by two instances of
>>>UnifiedClassLoader3. Once for the Class-Path entry in the EJB jar file
>>>(3eec1a, addedOrder=22) and once because it is present in the deploy
>>>directory  (bc9673, addedOrder=0)
>> 
>> 
>> I've tried removing the Class-Path entry from the manifest and now I get 
>> only a single class loader for the class (as I suspected I would). 
>> 
>> Should having a Class-Path entry in the manifest cause the use of a new 
>> class loader instance? I wouldn't have thought so.



-------------------------------------------------------
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