axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adrian Dick (JIRA)" <>
Subject [jira] Commented: (AXISCPP-723) SOAP Fault sent from server has wrong XML
Date Tue, 05 Jul 2005 07:56:10 GMT
    [ ] 

Adrian Dick commented on AXISCPP-723:


You are correct, the <appSpecific><detail> nodes within the SOAP detail node is
perfectly valid SOAP.
However, as part of the fix for AXISCPP-706 this structure was hard-coded into the axis-c
engine, which I believe is wrong.

The SOAP detail node should contain whatever structure is defined by the WSDL for a given
web service (or any XML where fault is not specified in the WSDL) - it may be the real problem
in the previous issue was incorrectly generated code, or a mis-understanding on how to use
that code.

> SOAP Fault sent from server has wrong XML
> -----------------------------------------
>          Key: AXISCPP-723
>          URL:
>      Project: Axis-C++
>         Type: Bug
>   Components: Server - Engine
>     Versions: 1.5 Final
>     Reporter: Samisa Abeysinghe

> When the C++ server throws a SOAP fault, I get the following XML:
> <detail><appSpecific><detail>AxisWsddException:Requested service not
> </appSpecific></detail>
> As you can notice, the use of "detail" tag is wrong here.
> Following is the ccomplete SOAP message sent by server:
> HTTP/1.1 200 OK
> Date: Fri, 01 Jul 2005 08:53:35 GMT
> Server: Apache/2.0.49 (Unix)
> Content-Length: 580
> Content-Type: text/xml
> <?xml version='1.0' encoding='utf-8' ?>
> <SOAP-ENV:Envelope xmlns:SOAP-ENV="" xmlns:xsd=""
> <SOAP-ENV:Body>
> <SOAP-ENV:Fault>
> <faultcode>SOAP-ENV:Client</faultcode>
> <faultstring>Requested service is not registerd at the server</faultstring>
> <faultactor>server name:listen port</faultactor>
> <detail><appSpecific><detail>AxisWsddException:Requested service not
> </appSpecific></detail>
> </SOAP-ENV:Fault>
> </SOAP-ENV:Body>
> </SOAP-ENV:Envelope>

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:

View raw message