Return-Path: 
 <dev-return-47329-apmail-cocoon-dev-archive=cocoon.apache.org@cocoon.apache.org>
Delivered-To: apmail-cocoon-dev-archive@www.apache.org
Received: (qmail 84481 invoked from network); 3 Sep 2003 16:45:45 -0000
Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12)
  by minotaur-2.apache.org with SMTP; 3 Sep 2003 16:45:45 -0000
Received: (qmail 6446 invoked by uid 500); 3 Sep 2003 16:19:57 -0000
Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org
Received: (qmail 6314 invoked by uid 500); 3 Sep 2003 16:19:55 -0000
Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:dev-help@cocoon.apache.org>
list-unsubscribe: <mailto:dev-unsubscribe@cocoon.apache.org>
list-post: <mailto:dev@cocoon.apache.org>
Reply-To: dev@cocoon.apache.org
Delivered-To: mailing list dev@cocoon.apache.org
Received: (qmail 6241 invoked from network); 3 Sep 2003 16:19:54 -0000
Received: from unknown (HELO host.leverageweb.com) (64.91.232.157)
  by daedalus.apache.org with SMTP; 3 Sep 2003 16:19:54 -0000
Received: from dhcp205059.hq.af.mil ([134.205.205.59] helo=leverageweb.com)
	by host.leverageweb.com with asmtp (Exim 3.36 #1)
	id 19uaJf-000757-00
	for dev@cocoon.apache.org; Wed, 03 Sep 2003 12:17:07 -0400
Message-ID: <3F5614AA.2090400@leverageweb.com>
Date: Wed, 03 Sep 2003 12:19:54 -0400
From: Geoff Howard <cocoon@leverageweb.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.3.1) Gecko/20030425
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: [VOTE] Migrate from the aging ECM
References: <LKENJPKDAIKAPKHEOCMMIEIHEPAA.cziegeler@s-und-n.de>
 <3F55ED13.5080601@apache.org> <3F55FD54.5070805@leverageweb.com>
 <3F5602D8.8010800@apache.org>
In-Reply-To: <3F5602D8.8010800@apache.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse,
 please include it with any abuse report
X-AntiAbuse: Primary Hostname - host.leverageweb.com
X-AntiAbuse: Original Domain - cocoon.apache.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [0 0]
X-AntiAbuse: Sender Address Domain - leverageweb.com
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

Berin Loritsch wrote:
> Geoff Howard wrote:
> 
>> Berin Loritsch wrote:
>>>
>>> In Cocoon/ECM we have the following constructs:
>>>
>>> <regular-component>
>>>   <stuff/>
>>> </regular-component>
>>>
>>> <database-selector>
>>>   <jdbc name="foo"/>
>>>   <j2ee name="bar"/>
>>>   <informix name="baz"/>
>>> </database-selector>
>>
>> Without a .roles file would we even have declarations that look like 
>> this?
> 
> :)  That IS with the ECM roles file.

Sorry, snipped the wrong part - the examples which followed were what I 
was looking at.

> However, with Fortress, you may be able to use a ROLEs file--but it 
> won't be
> necessary.  The meta info is part of the class, so there is only one 
> place you
> need to manage it (with the component implementation class).  The meta-info
> collection process will allow Fortress to automatically collect info 
> from other
> JARs for the available components--which means there won't need to be 
> any cludgy
> "user-roles" attributes any more.  Things just work.

Great - I think we're all looking forward to this.  I'm trying to get a 
handle on upgrade path for current users.  Sounds like we could acheive 
drop-in support for the old cocoon.xconf format complete with my.roles 
etc. but could switch the default cocoon.xconf (or whatever it would be 
then called) to the newer format?

Geoff