Return-Path: Delivered-To: apmail-jakarta-avalon-dev-archive@apache.org Received: (qmail 25123 invoked from network); 28 Jun 2002 06:44:13 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by 209.66.108.5 with SMTP; 28 Jun 2002 06:44:13 -0000 Received: (qmail 9150 invoked by uid 97); 28 Jun 2002 06:44:32 -0000 Delivered-To: qmlist-jakarta-archive-avalon-dev@jakarta.apache.org Received: (qmail 9114 invoked by uid 97); 28 Jun 2002 06:44:30 -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 9102 invoked by uid 98); 28 Jun 2002 06:44:30 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Message-ID: <3D1C0635.8030809@osm.net> Date: Fri, 28 Jun 2002 08:46:13 +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: Suggestions concerning the application profile XML Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: 209.66.108.5 1.6.2 0/1000/N X-Spam-Rating: 209.66.108.5 1.6.2 0/1000/N Pete: The current demonstration application profile in containerkit is: config.xml lalal I would like to change this to the following: application.xml // default name lalal Changes include: 1. applying the convention of a root element called "application" 2. all component declarations are contained within a "components" element 3. replace "impl" attribute with "class" to maintain consitency with the "class"/"type" convention 4. usage of the filename "application.xml" I'm not suggesting this as a standard but more along the lines of a convention that can/should be followed at this time. It will also allow me to switch test applications I'm working on with content in containerkit. I also interested in filtering out what are comon "application" level structures used in ECM/Fortress/Phoenix/Merlin (e.g. logging defintion, extension directories, etc.) - objective being to establish consitency in terminology and structure where possible in common areas. 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: