[
https://issues.apache.org/jira/browse/AXIS2C-837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Senaka Fernando updated AXIS2C-837:
-----------------------------------
Attachment: axis2.xml
diff.txt
Hi Michael and Dimuthu,
I have attached a modified version of the echo sample both client and service
as a diff, and the modified axis2.xml for you to test the same issue with the
echo sample. I think the issue lies with generated code or some other external
reason.
Please note that in SOAP 1.2, you set the soap action in the Content-Type
(MIME) header and not in a separate header as in SOAP 1.1. Also you have to use
axis2_options_set_soap_action() to set this header even in SOAP 1.2, and not
axis2_options_set_action().
Use TCPMon to monitor the payload. Shown below is the trace. Please not that
I'm not using the very same names that you use for your service and operation,
and I have run this test on the latest revision on the svn head which is
606548. So please update your copy if you are using a older revision.
POST /axis2/services/echo/echoString HTTP/1.1
User-Agent: Axis2/C
Content-Length: 125
Content-Type: application/soap+xml;charset=UTF-8;action="urn:echoString"
Host: 127.0.0.1:9090
<soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";>
<soapenv:Header/>
<soapenv:Body/></soapenv:Envelope>
HTTP/1.1 200 OK
Content-Type: application/soap+xml;charset=UTF-8
Content-Length: 197
<soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";>
<soapenv:Header/>
<soapenv:Body>
<DummyResponse>Echo service Dummy Response</DummyResponse>
</soapenv:Body></soapenv:Envelope>
Also, note that these attachments are not intended for inclusion.
Regards,
Senaka
> SOAPAction dispatching
> ----------------------
>
> Key: AXIS2C-837
> URL: https://issues.apache.org/jira/browse/AXIS2C-837
> Project: Axis2-C
> Issue Type: Bug
> Components: build system (Unix/Linux)
> Environment: Suse Linux 9.1, gcc 3.3, Axis Java nightly build
> Reporter: Michael Sutter
> Priority: Minor
> Fix For: Current (Nightly)
>
> Attachments: axis2.xml, diff.txt
>
>
> By accessing a c webservice with no parameters with a Java client to
> dispatching of the sent SOAP Action is not working. The Java client always
> get a Operation Not Found exception. The SOAP requests looks like this:
> POST /axis2/services/DAQStatus/getStatus HTTP/1.1
> Content-Type: application/soap+xml; charset=UTF-8; action="urn:getStatus"
> User-Agent: Axis2
> Host: 192.168.12.100:9090
> Transfer-Encoding: chunked
> 93
> <?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";><soapenv:Body
> /></soapenv:Envelope>
> 0
> So the SOAP Action is sent. To fix this in the client simply add the method
> to call to the request uri (shown above getStatus).
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
