[ http://issues.apache.org/jira/browse/AXISCPP-387?page=all ] Fred Preston closed AXISCPP-387: --------------------------------
> Bug with deserialiser when trying to deserialise a null object > -------------------------------------------------------------- > > Key: AXISCPP-387 > URL: http://issues.apache.org/jira/browse/AXISCPP-387 > Project: Axis-C++ > Type: Bug > Environment: n/a > Reporter: Fred Preston > Assignee: Fred Preston > > SOAP response message > --------------------- > <soapenv:Body> > <getMarketDataWebServiceResponse xmlns="http://ejb.framework...com";> > <getMarketDataWebServiceReturn> > <description xsi:nil="true" xmlns="http://objects.common.framework...com"/> > <id xmlns="http://objects.common.framework...com";>0</id> > <name xsi:nil="true" xmlns="http://objects.common...com"/> > <compCode xmlns="http://responseobjects.objects.common.framework...com";> > <description xmlns="http://objects.common.framework...com";>COMPCODE was never > set</description> > <id xmlns="http://objects.common.framework...com";>1000</id> > <name xmlns="http://objects.common.framework...com";>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: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
