cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Reinhard Poetz <>
Subject Re: [RT] Clarifying classloading in 2.2 [was Re: Classloader changes]
Date Tue, 11 Oct 2005 15:13:29 GMT
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.
> 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?

Reinhard Pötz           Independent Consultant, Trainer & (IT)-Coach 

{Software Engineering, Open Source, Web Applications, Apache Cocoon}


View raw message