Return-Path: 
 <geronimo-dev-return-3336-apmail-incubator-geronimo-dev-archive=incubator.apache.org@incubator.apache.org>
Delivered-To: apmail-incubator-geronimo-dev-archive@www.apache.org
Received: (qmail 80007 invoked from network); 9 Sep 2003 12:12:29 -0000
Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12)
  by minotaur-2.apache.org with SMTP; 9 Sep 2003 12:12:29 -0000
Received: (qmail 6435 invoked by uid 500); 9 Sep 2003 12:12:13 -0000
Delivered-To: apmail-incubator-geronimo-dev-archive@incubator.apache.org
Received: (qmail 6334 invoked by uid 500); 9 Sep 2003 12:12:11 -0000
Mailing-List: contact geronimo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:geronimo-dev-help@incubator.apache.org>
list-unsubscribe: <mailto:geronimo-dev-unsubscribe@incubator.apache.org>
list-post: <mailto:geronimo-dev@incubator.apache.org>
Reply-To: geronimo-dev@incubator.apache.org
Delivered-To: mailing list geronimo-dev@incubator.apache.org
Received: (qmail 6308 invoked from network); 9 Sep 2003 12:12:10 -0000
Received: from unknown (HELO george.toolazydogs.com) (166.84.147.110)
  by daedalus.apache.org with SMTP; 9 Sep 2003 12:12:10 -0000
Received: by customer.panix.com with Internet Mail Service (5.5.2653.19)
	id <RMAJNF5K>; Tue, 9 Sep 2003 08:23:20 -0400
Message-ID: <149246706FF1AF4996A41898AB453253117B@customer.panix.com>
From: Alan Cabrera <adc@toolazydogs.com>
To: "'geronimo-dev@incubator.apache.org'"
	 <geronimo-dev@incubator.apache.org>
Subject: RE: Geronimo Deployment Descriptors
Date: Tue, 9 Sep 2003 08:23:15 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
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


> -----Original Message-----
> From: Jeremy Boynes [mailto:jeremy@coredevelopers.net] 
> 
> To clarify, I think the spec defines deployment as the 
> process of taking a generic (vendor-neutral) assembled 
> application and getting it to run on a platform. The [J2EE] 
> spec sub-divides this into three tasks: Installation, 
> Configuration and Execution [pp 17]; the Deployment spec [88] 
> keeps the same concepts in a different order: Configuration, 
> Distribution and Start [pp 8]. This latter makes more sense 
> in a clustered environment.
> 
> I believe that the Deployment Descriptors are the 
> standardized input to the Configuration process. The 
> specification does not define what a platform's configuration 
> data looks like, allowing solutions such as WebLogic's where 
> is it stored in the archive as XML files, or solutions such 
> as WebSphere's where it is stored in a configuration repository.
> 
> There is no requirement for the platform to read the 
> deployment descriptor itself at runtime; a platform may 
> choose to do so (especially if that is the sole location for 
> configuration information, e.g. BEA or JBoss) but it is not required.
> 
> This allows us, if we wish, to pre-compile the configuration 
> information into other forms. For example, it could be an 
> archive of serialized MBean states that can simply be 
> unmarshalled by the server and started. This has many 
> potential advantages, such as reducing the startup time for 
> very large applications or reducing the resources required 
> for an embedded server.

This is obviously a compelling scenario.  I'm sold.


Alan