Parser gets confused when expected element is not there
-------------------------------------------------------
Key: AXISCPP-1064
URL: https://issues.apache.org/jira/browse/AXISCPP-1064
Project: Axis-C++
Issue Type: Bug
Components: Client - Deserialization
Reporter: nadir amra
Assignee: nadir amra
Fix For: current (nightly)
Currently, when an expected element is does not exist in the XML document, a
NULL is returned. However, this causes the parser to consume a node that has
not really been processed, which leads to erroneous errors.
I have confirmed that some java clients allow for expected elements to not be
sent.
So I will correct this problem by always doing a peek to see what the next
element before processing the element.
Add benefit to this is that it simplifies the generated code so that it no
longer does peeks for optional or nillable elements.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
