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="Service1">
> ...........................
> ............................
> </service>
> <service name="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="s1"> .. </service>
<service name="s2"> .. </service>
</services>
The deployment code can figure out which case it is based on the QName
of the document element.
Sanjiva.
