axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Charitha Kankanamge (JIRA)" <>
Subject [jira] Created: (AXIS2-1569) Inconsistent behavior in Axis2 service deployment
Date Wed, 01 Nov 2006 08:29:21 GMT
Inconsistent behavior in Axis2 service deployment

                 Key: AXIS2-1569
             Project: Apache Axis 2.0 (Axis2)
          Issue Type: Bug
          Components: deployment
    Affects Versions: 1.1
         Environment: Win XP, JDK 1.4
            Reporter: Charitha Kankanamge

Axis2 refers a service by its name when the service is defined within a service group. However
it uses the archive name, when the service is described in the service xml without specifying
a serviceGroup.

Steps to reproduce:
1. Deploy the attached 'sample-mtom' service archive. (sample-mtom.aar)
2. Look at its services.xml

<service name="MTOMSample">
<messageReceiver mep="" class="sample.mtom.service.MTOMSampleMessageReceiverInOut"/>
<parameter locked="false" name="ServiceClass">sample.mtom.service.MTOMSampleSkeleton</parameter>
<operation name="attachment" mep="">

3. Service can be seen in the admin console as 'MTOMSample' (This is the name of service inside
the service group)

4. Deploy the attached 'sample-swa' service archive. (sample-swa.aar)
5. Look at the services.xml
   <service name="SWASampleService">
        This is a sample Web Service for illustrating Attachments API of Axis2
    <parameter name="ServiceClass" locked="false">sample.soapwithattachments.service.AttachmentService</parameter>
    <operation name="uploadFile">
        <messageReceiver class="org.apache.axis2.rpc.receivers.RPCMessageReceiver"/>
6. In this case, service is displayed in the admin console as 'sample-swa' (This is the name
of archive)

Following solutions can be suggested to overcome this issue.

1. All the services should be defined using <serviceGroup>, even if the services.xml
contains only one service.
   Then the service can be displayed in the admin console by the specified service name in
2.  Throw a deployment error if service name and archive names are different in a single service

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message