axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fred Preston (JIRA)" <>
Subject [jira] Resolved: (AXISCPP-387) Bug with deserialiser when trying to deserialise a null object
Date Tue, 18 Jan 2005 11:53:17 GMT
     [ ]
Fred Preston resolved AXISCPP-387:

    Resolution: Fixed

This fix to SoapDeSerialiser.cpp appears to rectify the problem.

> Bug with deserialiser when trying to deserialise a null object
> --------------------------------------------------------------
>          Key: AXISCPP-387
>          URL:
>      Project: Axis-C++
>         Type: Bug
>  Environment: n/a
>     Reporter: Fred Preston
>     Assignee: Fred Preston

> SOAP response message
> ---------------------
> <soapenv:Body>
> <getMarketDataWebServiceResponse xmlns="">
> <getMarketDataWebServiceReturn>
> <description xsi:nil="true" xmlns=""/>
> <id xmlns="">0</id>
> <name xsi:nil="true" xmlns=""/>
> <compCode xmlns="">
> <description xmlns="">COMPCODE was never set</description>
> <id xmlns="">1000</id>
> <name xmlns="">COMPCODE_NOTSET</name>
> </compCode>
> This response message was not being parsed properly because the deserialiser was getting
stuck on the 'description' label because it had nil="true", the next element parsed was not
what was expected (expected CHARACTER, got END).  Thus the m_pNode pointer was not being moving
forward through the message and consequently all the other fields where null.  This can be
rectified by nilling the pointer so that on the next element, the message is resynchronised.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
If you want more information on JIRA, or have a bug to report see:

View raw message