Return-Path: 
 <dev-return-25385-apmail-geronimo-dev-archive=geronimo.apache.org@geronimo.apache.org>
Delivered-To: apmail-geronimo-dev-archive@www.apache.org
Received: (qmail 1379 invoked from network); 15 Feb 2006 01:04:15 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 15 Feb 2006 01:04:15 -0000
Received: (qmail 23392 invoked by uid 500); 15 Feb 2006 01:04:11 -0000
Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org
Received: (qmail 23353 invoked by uid 500); 15 Feb 2006 01:04:11 -0000
Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:dev-help@geronimo.apache.org>
list-unsubscribe: <mailto:dev-unsubscribe@geronimo.apache.org>
List-Post: <mailto:dev@geronimo.apache.org>
Reply-To: dev@geronimo.apache.org
List-Id: <dev.geronimo.apache.org>
Delivered-To: mailing list dev@geronimo.apache.org
Received: (qmail 23342 invoked by uid 99); 15 Feb 2006 01:04:11 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Feb 2006 17:04:11 -0800
X-ASF-Spam-Status: No, hits=0.5 required=10.0
	tests=DNS_FROM_RFC_ABUSE
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Received: from [216.136.174.138] (HELO smtp100.mail.sc5.yahoo.com)
 (216.136.174.138)
    by apache.org (qpsmtpd/0.29) with SMTP; Tue, 14 Feb 2006 17:04:10 -0800
Received: (qmail 39890 invoked from network); 15 Feb 2006 01:03:50 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=Received:Mime-Version:Content-Transfer-Encoding:Message-Id:Content-Type:To:From:Subject:Date:X-Mailer;
  b=E8bRtDyrWr8HQY+KQ9w1lQVwTtKDe5T6H/yeyfIxTUl6M4wlqHKp0YmBPdEaQushswHEL3dECpMTNWEG9sLvYv1hbTa5tcPqyUrohVmXIxGouWQUqJO0wmFrpZmA15fwxniIsBJce0eNBfl7O3Gh4Cx7M0ANMYQpMlXWt7AEABA=
  ;
Received: from unknown (HELO ?192.168.1.5?) (david?jencks@66.93.38.137 with
 plain)
  by smtp100.mail.sc5.yahoo.com with SMTP; 15 Feb 2006 01:03:49 -0000
Mime-Version: 1.0 (Apple Message framework v746.2)
Content-Transfer-Encoding: 7bit
Message-Id: <303EF7CE-85AE-490B-9676-679E0727FFE8@yahoo.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: dev@geronimo.apache.org
From: David Jencks <david_jencks@yahoo.com>
Subject: Sample plan bits for configId branch, please review!
Date: Tue, 14 Feb 2006 17:03:47 -0800
X-Mailer: Apple Mail (2.746.2)
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

We need some widespread thought about the new xml schema we're  
getting in 1.1.   Dain and I are not particularly thrilled with the  
element names but haven't thought of improvements.  We also thought  
of an alternate way of presenting the info and would like opinions on  
which is better.

The schema currently in svn in the configid branch results in plans  
that start like this:

<configuration xmlns="http://geronimo.apache.org/xml/ns/deployment-1.1">
   <environment>
     <configId>
       <groupId>geronimo</groupId>
       <type>car</type>
       <artifactId>geronimo-gbean-deployer</artifactId>
       <version>1.0.1-SNAPSHOT</version>
     </configId>
<!-- name-key elements are very unlikely to be used by anything  
except "root" system plans
such as j2ee-system.  Included here only to show what they look like -->
     <name-key>
       <key>domain</key>
       <value>geronimo.maven</value>
     </name-key>
     <name-key>
       <key>J2EEServer</key>
       <value>geronimo</value>
     </name-key>
     <classloader>
       <import>
         <groupId>geronimo</groupId>
         <type>car</type>
         <artifactId>geronimo-system</artifactId>
         <version>1.0.1-SNAPSHOT</version>
       </import>
       <dependency>
         <groupId>geronimo</groupId>
         <artifactId>geronimo-common</artifactId>
         <version>1.0.1-SNAPSHOT</version>
       </dependency>
       <include>
         <groupId>geronimo</groupId>
         <artifactId>geronimo-deployment</artifactId>
         <version>1.0.1-SNAPSHOT</version>
       </include>
     </classloader>
<!--reference is a new element, the meaning is that the configuration  
must be loaded and started before this one, but the classloader of  
the config is not a parent -->
     <reference>
       <groupId>geronimo</groupId>
       <type>car</type>
       <artifactId>geronimo-j2ee</artifactId>
       <version>1.0.1-SNAPSHOT</version>
     </reference>
   </environment>
   <!--Deployer used to process modules and plans-->
   <gbean name="Deployer"  
class="org.apache.geronimo.deployment.Deployer">


An alternate layout is more similar to m2 with the idea of different  
functions for a dependency shown by a "scope" element.  Scope doesn't  
seem like the right element name for us. (sorry about the lousy  
indenting)

<configuration xmlns="http://geronimo.apache.org/xml/ns/deployment-1.1">
   <environment>
     <configId>
       <groupId>geronimo</groupId>
       <type>car</type>
       <artifactId>geronimo-gbean-deployer</artifactId>
       <version>1.0.1-SNAPSHOT</version>
     </configId>
<!-- name-key elements are very unlikely to be used by anything  
except "root" system plans
such as j2ee-system.  Included here only to show what they look like -->
     <name-key>
       <key>domain</key>
       <value>geronimo.maven</value>
     </name-key>
     <name-key>
       <key>J2EEServer</key>
       <value>geronimo</value>
     </name-key>
       < dependency>
         <groupId>geronimo</groupId>
         <type>car</type>
         <artifactId>geronimo-system</artifactId>
         <version>1.0.1-SNAPSHOT</version>
         <scope>full</scope>
       </dependency>
       <dependency>
         <groupId>geronimo</groupId>
         <artifactId>geronimo-common</artifactId>
         <version>1.0.1-SNAPSHOT</version>
         <scope>class</scope>
       </dependency>
       < dependency>
         <groupId>geronimo</groupId>
         <artifactId>geronimo-deployment</artifactId>
         <version>1.0.1-SNAPSHOT</version>
         <scope>include</scope>
       </dependency>
     < dependency>
       <groupId>geronimo</groupId>
       <type>car</type>
       <artifactId>geronimo-j2ee</artifactId>
       <version>1.0.1-SNAPSHOT</version>
       <scope>service</scope>
    </dependency>
   </environment>
   <!--Deployer used to process modules and plans-->
   <gbean name="Deployer"  
class="org.apache.geronimo.deployment.Deployer">

Here, the scopes have meaning as follows:

both -- both classes and services (gbeans), like import
classes -- only classes, if a car don't start the gbeans for us, like  
dependency
services -- only gbeans, don't add classes to our classpath, like  
reference (new element shown in first example)
include -- copy the artifact into the current configuration.  This  
seems like a separate dimension not related to the previous scopes.

Again, please study these and comment.

Many thanks
david jencks