Return-Path: Delivered-To: apmail-jakarta-avalon-phoenix-dev-archive@apache.org Received: (qmail 64216 invoked from network); 15 Sep 2002 01:57:56 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 15 Sep 2002 01:57:56 -0000 Received: (qmail 12856 invoked by uid 97); 15 Sep 2002 01:58:40 -0000 Delivered-To: qmlist-jakarta-archive-avalon-phoenix-dev@jakarta.apache.org Received: (qmail 12840 invoked by uid 97); 15 Sep 2002 01:58:39 -0000 Mailing-List: contact avalon-phoenix-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Avalon-Phoenix Developers List" Reply-To: "Avalon-Phoenix Developers List" Delivered-To: mailing list avalon-phoenix-dev@jakarta.apache.org Received: (qmail 12823 invoked by uid 98); 15 Sep 2002 01:58:39 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Content-Type: text/plain; charset="iso-8859-1" From: Peter Donald To: "Avalon-Phoenix Developers List" Subject: Re: kernal.xml vs. assembly.xml format Date: Sun, 15 Sep 2002 12:02:04 +1000 User-Agent: KMail/1.4.2 References: <000d01c25c17$806808a0$c600a8c0@dellinspiron> In-Reply-To: <000d01c25c17$806808a0$c600a8c0@dellinspiron> X-Wisdom: A right is not what someone gives you; it's what no one can take from you. MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200209151202.04823.peter@apache.org> X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Sun, 15 Sep 2002 03:52, David Weitzman wrote: > This is just something to consider. > > I've noticed that kernal.xml and assembly config files express similar > information, but use a different format ( nested in > vs. ). One is parsed by DefaultEmbeddor, the other by Assembler= =2E > > There are some distinct differences. allows you to specify= and > object's role, whereas dependancies in s use bock names and > to add stuff to the ServiceManager. Assembler is also tied t= o > the .sar format. > > But overall, basically, the files are similar. Is this a bad thing, go= od > thing, or just a thing? At the moment it is just a thing. Note that kernel.xml also allows you to= =20 specify configuration data in xml rather than separately (ie in=20 SAR-INF/config.xml). In the future I think it would be desirable that the format become a lot = more=20 homogenized. When we get around to implementing=20 http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3D12411 I hope we will find a format that is consistent and easy to use. Eventual= ly I=20 believe that the kernel will be just a container that hosts other contain= ers.=20 So the deployment format of the kernel will hopefully endup being very=20 similar to the deployment format of applications. --=20 Cheers, Peter Donald ----------------------------------------------------- When a stupid man is doing something he's ashamed of,=20 he always declares that it is his duty. =09=09=09=09=09George Bernard Shaw=20 ----------------------------------------------------- -- To unsubscribe, e-mail: For additional commands, e-mail: