cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Reinhard Poetz <>
Subject Re: [RT] Cocoonlet
Date Thu, 28 Apr 2005 05:32:49 GMT
Vadim Gritsenko wrote:
> Daniel Fagerstrom wrote:
>> Our current (controversial ;) ) plan is to consider the sitemap and 
>> the component aspect of the original block proposal as separate 
>> concerns and (at least initially) solve them separately.
> I propose less controversial plan.
> As the first step, implement what you call "sitemap blocks", but call 
> them simply "blocks". Own classloader, full classloading isolation, 
> block protocol, exposing direct sitemap components: generators, 
> transformers, serializers.
> As the second step, implement "components block" *on top of* "sitemap 
> blocks". This introduces second classloader (one is public, to share 
> component interfaces, and one is private, to contain components 
> implementation and libraries), and logic for managing classloader trees. 
> Still call it simply "block".

I absolutly agree with your plan Vadim!

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

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


View raw message