Return-Path: 
 <dev-return-30199-apmail-geronimo-dev-archive=geronimo.apache.org@geronimo.apache.org>
Delivered-To: apmail-geronimo-dev-archive@www.apache.org
Received: (qmail 72539 invoked from network); 28 May 2006 17:05:52 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 28 May 2006 17:05:52 -0000
Received: (qmail 87521 invoked by uid 500); 28 May 2006 17:05:49 -0000
Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org
Received: (qmail 87480 invoked by uid 500); 28 May 2006 17:05:49 -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 87469 invoked by uid 99); 28 May 2006 17:05:49 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 28 May 2006 10:05:49 -0700
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: domain of ammulder@gmail.com designates
 64.233.184.236 as permitted sender)
Received: from [64.233.184.236] (HELO wr-out-0506.google.com) (64.233.184.236)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 28 May 2006 10:05:48 -0700
Received: by wr-out-0506.google.com with SMTP id i7so733965wra
        for <dev@geronimo.apache.org>; Sun, 28 May 2006 10:05:27 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth;
        b=Tcg8YQ8htSYOe4SivVKOF0FEL0sr6EGgGrj4uGSJwbnj0VYHV2XP2lr1ZY85w8wBz0R0oFljBIhluH1P4TEUtTKtqLjnZHPLoTD54JEAUdji9+ZhFha/pe7FgNV076bw8leGvoSZFxz1x8o1tgrROvX5i+KVHyT27IeiMWhx5Os=
Received: by 10.64.3.9 with SMTP id 9mr2675604qbc;
        Sun, 28 May 2006 10:05:27 -0700 (PDT)
Received: by 10.65.176.15 with HTTP; Sun, 28 May 2006 10:05:27 -0700 (PDT)
Message-ID: <74e15baa0605281005t2c2967d3q756eadee58d768ba@mail.gmail.com>
Date: Sun, 28 May 2006 13:05:27 -0400
From: "Aaron Mulder" <ammulder@alumni.princeton.edu>
Sender: ammulder@gmail.com
To: "Geronimo Dev" <dev@geronimo.apache.org>
Subject: Support for different modules types in EAR
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-Google-Sender-Auth: b78f0756786da844
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

Any objections to supporting different module types (such as Geronimo
service JARs or future Spring or ServiceMix JARs) within an EAR?  For
example, this would let you create an EAR with a normal EJB JAR, a
normal web app WAR, and a Geronimo service JAR containing GBeans used
by the EJBs or web app (or that just run when the app runs).

To do this, I figure we'd just let you specify additional modules in
the geronimo-application.xml, even if you're not going to provide a
plan for them.  So it would be something like this:

application.xml

<application>
  <module><ejb>foo.jar</ejb></module>
  <module><web>...</web></module>
</application>

geronimo-application.xml

<application>
  <module>
    <other>bar.jar</other>
  </module>
</application>

Where a plan like this indicates that there are no overrides for the
EJB or Web app, but we're adding another module, bar.jar, with
unspecified type.  That should be OK since during deployment we ask
all the config builders whether they can handle the specified module,
so we'll figure out whether we can handle it, and if so, what type of
module it is (based on what deployment descriptors / plans it
contains).

Thanks,
    Aaron