axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Sutter (JIRA)" <>
Subject [jira] Commented: (AXIS2C-837) SOAPAction dispatching
Date Thu, 27 Dec 2007 18:02:46 GMT


Michael Sutter commented on AXIS2C-837:

Hello Senaka,

sorry for the late reply - but I'm on my Christmas vacations. I raised the Jira because of
the discussion on the Axis2C user list and the problem that I can't access my service with
the generated client.

But as far as I understand you found the error and raised another Jira - thanks for that.

Regards Michael

> SOAPAction dispatching
> ----------------------
>                 Key: AXIS2C-837
>                 URL:
>             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:
> Transfer-Encoding: chunked
> 93
> <?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope xmlns:soapenv=""><soapenv:Body
> 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:
For additional commands, e-mail:

View raw message