axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amila Chinthaka Suriarachchi (JIRA)" <>
Subject [jira] Commented: (AXIS2-2389) Dispatching based on the SOAP message body does not work for document/literal style
Date Thu, 06 Sep 2007 05:07:33 GMT


Amila Chinthaka Suriarachchi commented on AXIS2-2389:

I invoke a service with your wsdl with this request which does not have any soap actions

POST /axis2/services/EchoApiService HTTP/1.1

Content-Type: application/soap+xml; charset=UTF-8

User-Agent: Axis2


Transfer-Encoding: chunked


<?xml version='1.0' encoding='UTF-8'?>
   <soapenv:Envelope xmlns:soapenv="">
         <ns1:EchoRequest xmlns:ns1="">

and it worked fine.

Can you send your request and full stack trace.

> Dispatching based on the SOAP message body does not work for document/literal style
> -----------------------------------------------------------------------------------
>                 Key: AXIS2-2389
>                 URL:
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: kernel
>    Affects Versions: 1.1.1
>         Environment: Axis2, version 1.1.1
> Tomcat 5.0
> JDK1.6.0
>            Reporter: Jonas Bo√ęthius
>            Assignee: Amila Chinthaka Suriarachchi
>            Priority: Blocker
>             Fix For: 1.3
>         Attachments: EchoApi.wsdl
> I am using a document/literal service and found that the dispatching based on the message
body does not seem to work. Any SOAPAction header except the one defined in the WSDL causes
the following fault:
>      org.apache.axis2.AxisFault: Operation Not found EPR is...
> I've used ADB data binding and generated server side classes and services.xml using the
WSDL2Java utility.
> When debugging, I can see that the SOAPMessageBodyBasedDispatcher
>  is invoked for the dispatching, that it finds the correct request element name but when
passing the call to the getOperation method in the AxisService class, the operationsAliasesMap
does not contain the name of the request element. It seems like the initialization of the
operationsAliasesMap does not consider the case needed for the SOAPMessageBodyBasedDispatcher.
> Found an easy work-around of manually adding the name of the request root element as
actionMapping in the generated services.xml file. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

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

View raw message