cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ugo Cei <...@apache.org>
Subject Re: [RT] Some notes about the "Real Blocks" issue
Date Fri, 15 Oct 2004 19:49:41 GMT
Il giorno 15/ott/04, alle 20:18, Vadim Gritsenko ha scritto:

> Ugo Cei wrote:
>> Il giorno 15/ott/04, alle 13:01, Vadim Gritsenko ha scritto:
>>> The best plan IMHO would be:
>>>
>>> 1. Remove ECM - implementation of Avalon container. Keep re-usable 
>>> components code (XSLT, Source, Store, etc).
>>> 2. Drop in the container which replaces it.
>>> 3. Write bridge code between container in (2) and (1).
>>> 4. Test.
>>> 5. Release Cocoon 2.3.
>>> 6. Continue with usual Cocoon development: improvements, 
>>> refactorings, as you see fit: rewrite source resolving or sitemap 
>>> processor or whatever you want if you have time for it.
>>>
>>> For a useful example of 6, Store implementation should plug in into 
>>> Java 1.5 management API instead of having background checker thread.
>> Looks like a very good plan to me.
>
> Do you have suggestions for (3)? Particularly, how AvalonBeanFactory 
> should be implemented, and what should be the basis for 
> ComponentSelectors?

Er, no. Actually what I proposed was to keep the two containers (ECM 
and the new one) separate, instead of emulating or wrapping the former 
inside the latter.

	Ugo

-- 
Ugo Cei - http://beblogging.com/

Mime
View raw message