Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Message-ID: <41701465.5080909@reverycodes.com>
Date: Fri, 15 Oct 2004 14:18:13 -0400
From: Vadim Gritsenko <vadim@reverycodes.com>
User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: [RT] Some notes about the "Real Blocks" issue
References: <0MKv6A-1CIMeE12BG-0003C1@mx.perfora.net>
 <416FADFD.3030308@reverycodes.com>
 <5A289114-1EA4-11D9-8A87-000A95DC4186@apache.org>
In-Reply-To: <5A289114-1EA4-11D9-8A87-000A95DC4186@apache.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

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?

Vadim