Return-Path: Delivered-To: apmail-jakarta-avalon-dev-archive@apache.org Received: (qmail 50215 invoked from network); 25 Sep 2002 01:56:20 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 25 Sep 2002 01:56:20 -0000 Received: (qmail 20615 invoked by uid 97); 25 Sep 2002 01:57:05 -0000 Delivered-To: qmlist-jakarta-archive-avalon-dev@jakarta.apache.org Received: (qmail 20565 invoked by uid 97); 25 Sep 2002 01:57:04 -0000 Mailing-List: contact avalon-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Avalon Developers List" Reply-To: "Avalon Developers List" Delivered-To: mailing list avalon-dev@jakarta.apache.org Received: (qmail 20544 invoked by uid 98); 25 Sep 2002 01:57:03 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Message-ID: <3D9117B9.7030909@apache.org> Date: Wed, 25 Sep 2002 03:56:09 +0200 From: Stephen McConnell User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.0.0) Gecko/20020530 X-Accept-Language: en, en-us MIME-Version: 1.0 To: Avalon Developers List Subject: Re: stable Fortress? References: <200209242327.44009.peter@apache.org> <000101c263d1$891d7900$94a85982@LSD> <20020924141545.GA27408@fztig938.bank.dresdner.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Marcus Crafter wrote: >On Tue, Sep 24, 2002 at 03:51:46PM +0200, Leo Simons wrote: > > >>However, I think it would be a shame if it means that a future >>fortress, or "merlin's fortress" as talked about before, would >>need to provide yet more compatibility with old materials (ie >>with ECM *and* fortress1). I am not familiar enough with fortress >>to make this estimate. >> >> > > I'm not familiar enough either, but I still feel that we're > reinventing the wheel with both Fortress and Merlin continuing as > separate containers. > > I know there's been progress at unifying the common ground with the > container/ and meta/ subprojects - but I would so much rather 1 > container to work on rather than having to choose between the 2 (as is > currently happening on cocoon-dev). > > Berin, why don't we just make Fortress' MetaDataContainer extend > from Merlin's DefaultContainer and have it provide Fortress style > semantics ? > This is completely achivable. The ability to plug in a custom lifestyle manager is already in place - which would be needed to take care of the particular semntics implied by ECM components. Cheers, Steve. -- Stephen J. McConnell OSM SARL digital products for a global economy mailto:mcconnell@osm.net http://www.osm.net -- To unsubscribe, e-mail: For additional commands, e-mail: