[
https://issues.apache.org/jira/browse/AXISCPP-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wayne Johnson updated AXISCPP-1015:
-----------------------------------
Attachment: Axis1015-3.diff
OK, forget about my earlier patch (Axis1015-2). This is a replacement for it.
Basically the same problem I ran into in the original problem exists in
SoapDeSerializer::getBasicArray(). If the array has no elements, we fail to
skip over the end element, thus causing the next elements to get out of
sequence.
This had me puzzled for a while till I realized that the soap elements are
different for a null array vs. a zero length array.
> Error deserializing empty array within a structure
> --------------------------------------------------
>
> Key: AXISCPP-1015
> URL: https://issues.apache.org/jira/browse/AXISCPP-1015
> Project: Axis-C++
> Issue Type: Bug
> Components: Serialization
> Affects Versions: 1.6 Beta
> Environment: Sending response from Java AXIS Server
> Reporter: Wayne Johnson
> Fix For: current (nightly)
>
> Attachments: Axis1015-2.diff, Axis1015-3.diff, SOAP-1015.xml,
> SoapDeSerializer.patch, SWS.wsdl
>
>
> I am returning a structure that contains an array of structures. If I return
> that array with no elements, the SoapDeSerializer::getArraySize method
> returns a -1.
>
> Then SoapDeSerializer::getCmplxArray falls into the error path, and returns
> AXIS_FAIL. My stub deserializer for the outside structure sees the FAIL
> status and returns the FAIL to SoapDeSerializer::getCmplxObject and
> everything percolates back to my client where a NULL is returned to the
> client instead of my structure.
> The same SOAP response seems to work fine on the Axis Java client.
> I'm working on the svn trunk.
> Thanks.
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
