axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "nadir amra (JIRA)" <>
Subject [jira] Resolved: (AXISCPP-1029) A non SOAP response results in client crashing
Date Sat, 21 Apr 2007 19:05:15 GMT


nadir amra resolved AXISCPP-1029.

    Resolution: Fixed

In SoapDeSerializer::getEnvelope(), I updated the code to throw an exception if the element
name is not Envelope. 

In addition, in SoapDeSerializer::getBody() and SoapDeSerializer::getHeader(), I added a check
to ensure that the SOAP version is valid prior to comparing the element name to SOAP element
names SKW_HEADER and SKW_BODY.  The check is as follows:

(m_nSoapVersion != VERSION_LAST)

I will wait to close until I build a testcase. 

> A non SOAP response results in client crashing
> ----------------------------------------------
>                 Key: AXISCPP-1029
>                 URL:
>             Project: Axis-C++
>          Issue Type: Bug
>          Components: Client - Deserialization
>    Affects Versions: current (nightly)
>            Reporter: nadir amra
>         Assigned To: nadir amra
>             Fix For: current (nightly)
> If a response returns that is not a SOAP response, then the client crashes in SoapDeSerializer::getHeader
> For example, if a service returns simply an HTML response:
> HTTP/1.1 500 Internal Server Error
> Connection: close
> Date: Fri, 20 Apr 2007 20:51:44 GMT
> Server: Microsoft-IIS/6.0
> Content-Type: text/html
> <html><head><title>Failure</title></head>
> <body><h2>Failed to connect</h2>
> </body>
> </html>
> We should be a little bit more resilient and throw an exception....

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