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-1615) List service as faulty when an invalid transport is specified in the services.xml
Date Mon, 06 Nov 2006 08:09:37 GMT
List service as faulty when an invalid transport is specified in the services.xml

                 Key: AXIS2-1615
             Project: Apache Axis 2.0 (Axis2)
          Issue Type: Bug
          Components: deployment
    Affects Versions: 1.1
         Environment: Win XP, JDK 1.5, apache tomcat 5.5.16
            Reporter: Charitha Kankanamge
            Priority: Minor

I defined the following services.xml and bundled it with the relevant service implementation
class in an archive.
Archive was deployed successfuly and listed as a valid service in the admin console.

<service name="Servicetest" targetNamespace="">
    <description> The description of the service </description>  

     <schema schemaNamespace=""/> 
     <parameter name="ServiceClass" locked="xsd:false">com.test.Servicetest</parameter>
    <operation name="mathoperation"> 
        <messageReceiver class="org.apache.axis2.rpc.receivers.RPCMessageReceiver"/>

However I have noticed that the 'service' element is empty in the generated wsdl.

This occured due to an invalid transport specified in the services.xml. Because of that, the
service should have been listed as a faulty service in admin console.

Steps to reproduce:
1. Deploy the attached service archive
2. Access axis2 admin console
3. Click on the service (servicetest)
4. wsdl file is displayed

You can see an empty 'service' element in there. 

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