cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vadim Gritsenko <>
Subject Re: [RT] Clarifying classloading in 2.2 [was Re: Classloader changes]
Date Tue, 11 Oct 2005 15:58:04 GMT
Reinhard Poetz wrote:
> Carsten Ziegeler wrote:
>> Reinhard Poetz wrote:
>>> The problem is, that going for what you propose would mean that each 
>>> block has to get its own classloader. In Amsterdam we only talked 
>>> about *one global* classloader for Cocoon, but maybe I'm wrong here.

Somebody has a picture of a whiteboard with class loaders hierarchy.

>> No, you're right - I was refering to "real blocks" with OSGi and then we
>> have a class loader for each block. And this class loader will be
>> "paranoid", so my point is that we can already make the "one
>> classloader" "paranoid".
> We both agree here, Vadim is against :-p
> Well, we could make this configureable, but what does it really buy us?

Not so much against, but I think that adding a class loader on a block level 
makes it unnecessary to have global cocoon class loader, isn't it?


View raw message