Return-Path: Delivered-To: apmail-jakarta-avalon-dev-archive@apache.org Received: (qmail 22665 invoked from network); 26 Aug 2002 11:08:16 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 26 Aug 2002 11:08:16 -0000 Received: (qmail 13288 invoked by uid 97); 26 Aug 2002 11:08:42 -0000 Delivered-To: qmlist-jakarta-archive-avalon-dev@jakarta.apache.org Received: (qmail 13240 invoked by uid 97); 26 Aug 2002 11:08:41 -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 13228 invoked by uid 98); 26 Aug 2002 11:08:40 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Message-ID: <3D6A0C07.9050902@apache.org> Date: Mon, 26 Aug 2002 13:07:51 +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: common attributes revisited (Re: BlockContext & Merlin.) References: <3D677832.20604@yahoo.com> <200208250354.42938.peter@apache.org> <3D67DE8C.6030901@apache.org> <200208251124.48246.peter@apache.org> <1030273481.10036.14.camel@lsd.bdv51> 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 Leo Simons wrote: >>>Given that there is work ongoing concerning a common set of attributes >>>and keys, is it likely that the changes in Phoenix will be synchronized >>>with other Avalon projects? In particular, could someone involved in >>>Phoenix comment on the proposed attribute and context key values >>>published under the excalibur/container package? >>> >>> >>They are different from the ones I am working on. I will publish the >>attributes/key names that Phoenix will use when they are closer to being >>complete. >> >> > >I'd suggest against such a process flow. Since I am sure I will be using >my components in different containers in the future, I want these key >names to be the same, especially since I can see no reason not to make >them the same. I urge you to consolidate efforts now. > >Discussion may be tiring, but with issues like this, it is important we >figure things out sooner rather than later (when it is all in a released >product and impossible to change). > > +1 Leo: I've put together documentation concerning all of the keys and type level attributes that I consider to be cross-container related. The documentation has been put under the excalibur/container package in the xdocs directory. The documentation is intended to provide information/proposals about common container keys, attributes, services, etc. and is not intended to be specific to any particular container. To build the docs just use the "ant xdocs" target then checkout the generated html in build/docs. Cheers, Steve. > >cheers, > >Leo > > > >-- >To unsubscribe, e-mail: >For additional commands, e-mail: > > > -- 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: