Return-Path: 
 <axis-dev-return-38863-apmail-ws-axis-dev-archive=ws.apache.org@ws.apache.org>
Delivered-To: apmail-ws-axis-dev-archive@www.apache.org
Received: (qmail 86099 invoked from network); 13 Sep 2005 15:04:25 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 13 Sep 2005 15:04:25 -0000
Received: (qmail 44740 invoked by uid 500); 13 Sep 2005 15:04:21 -0000
Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org
Received: (qmail 44711 invoked by uid 500); 13 Sep 2005 15:04:21 -0000
Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
list-help: <mailto:axis-dev-help@ws.apache.org>
list-unsubscribe: <mailto:axis-dev-unsubscribe@ws.apache.org>
List-Post: <mailto:axis-dev@ws.apache.org>
List-Id: <axis-dev.ws.apache.org>
Delivered-To: mailing list axis-dev@ws.apache.org
Received: (qmail 44693 invoked by uid 99); 13 Sep 2005 15:04:20 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Sep 2005 08:04:20 -0700
X-ASF-Spam-Status: No, hits=0.9 required=10.0
	tests=DNS_FROM_RFC_ABUSE,DNS_FROM_RFC_WHOIS
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Received: from [216.104.212.90] (HELO p01mgw01.macromedia.com)
 (216.104.212.90)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Sep 2005 08:04:30 -0700
Received: from P01EXF01.macromedia.com (ms-exchange.macromedia.com
 [10.176.24.139])
	by p01mgw01.macromedia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id
 j8DF4IBw007079
	for <axis-dev@ws.apache.org>; Tue, 13 Sep 2005 08:04:18 -0700 (PDT)
Received: from p02exm01.macromedia.com ([10.60.48.130]) by
 P01EXF01.macromedia.com with Microsoft SMTPSVC(6.0.3790.211);
	 Tue, 13 Sep 2005 08:03:59 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Axis2] More about service groups
Date: Tue, 13 Sep 2005 11:04:10 -0400
Message-ID: <39A72E1EBF03EB44AACFD8036D1489F9014134AE@p02exm01.macromedia.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Axis2] More about service groups
Thread-Index: AcW4PyYtxBzb1vG6RAKenAc6PmAfggANSmhg
From: "Tom Jordahl" <tomj@macromedia.com>
To: <axis-dev@ws.apache.org>
X-OriginalArrivalTime: 13 Sep 2005 15:03:59.0453 (UTC)
 FILETIME=[5EB478D0:01C5B874]
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N


How about naming the element <serviceGroup> in the service.xml to make
it more distinctive from <service>.

That would match with the code too.

--
Tom Jordahl
Macromedia Server Development

> -----Original Message-----
> From: Deepal Jayasinghe [mailto:deepal@opensource.lk]
> Sent: Tuesday, September 13, 2005 4:42 AM
> To: axis-dev@ws.apache.org
> Subject: Re: [Axis2] More about service groups
>=20
> Hi all;
>=20
> +1 for proposal ,
>=20
> But I have some comments ,
> rather than introducing new description file I like to have
service.xml
> insider archive file and which root element can either be <service> or
> <services> , if the root element is <service> I will create
> ServiceGroupDescription by giving archive name as group name and the
group
> only contain one service. In the other hand if the root element is
> <services> ServiceGruopDescription will be created by giving archive
name
> as
> Service Group name and all the service in service.xml will belong to
that
> service group.
>=20
>=20
>=20
> Thanks,
>  Deepal
> ................................................................
> ~Future is Open~
>=20
> ----- Original Message -----
> From: "Sanjiva Weerawarana" <sanjiva@opensource.lk>
> To: <axis-dev@ws.apache.org>
> Sent: Tuesday, September 13, 2005 10:00 AM
> Subject: Re: [Axis2] More about service groups
>=20
>=20
> > On Tue, 2005-09-13 at 09:49 +0600, Deepal Jayasinghe wrote:
> >>         I think we do not need to introduce new archive file or
> >>         description to solve this problem , so my idea is this
> >>         no matter archive file contain a service or service-group,
the
> >>         archive file contain service.xml and the it will be like
that
> >>
> >>         <services >
> >>           <service name=3D"Service1">
> >>             ...........................
> >>             ............................
> >>           </service>
> >>           <service name=3D"Service2">
> >>              ...........................
> >>              ............................
> >>           </service>
> >>         </services>
> >>
> >>         So the existing service.xml has to change to this format,
> >>
> >>         and the name of the archive file will be that name of the
> >>         service group , if the name of the archive file is foo.aar
> >>         then service-group name will be "foo" and the epr of the
> >>         services will    axis2/services/foo:Service1
> >>          and  axis2/services/foo:Service2
> >>
> >>
> >>         In addition to that META-INF folder can contain any number
of
> >>         wsdl file , in this case that can contain
> >>         Service1.wsdl , Service2.wsdl in that case
ServiceDescriptions
> >>         will be created using WSDLs and overide and configure using
> >>         srevice.xml
> >
> > This works for the case of >1 service per aar. But what about the
simple
> > case? Doesn't this force the user to come up with 2 names in that
case-
> > one for the .aar file and one for the service?? If so that's ugly
...
> >
> > An alternative is to use one file service.xml (or rename to
> > package.xml ??) which contains either
> > <service> .. </service>
> > or
> > <services>
> > <service name=3D"s1"> .. </service>
> > <service name=3D"s2"> .. </service>
> > </services>
> >
> > The deployment code can figure out which case it is based on the
QName
> > of the document element.
> >
> > Sanjiva.
> >
> >
>=20