[
https://issues.apache.org/jira/browse/AXISCPP-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12615412#action_12615412
]
nadiramra edited comment on AXISCPP-888 at 7/21/08 1:45 PM:
-------------------------------------------------------------
In the complex type derializer, we now doa peek at the very end to ensure we
are at the end of element.
In the stub code, after all the deserialization, a stub method call to
checkForExtraneousElements() is performed that basically does the same thing.
The stub for RPC does not invoke checkForExtraneousElements(). Was not sure if
applicable since bulk of our test cases are for doc/literal.
Will wait to close once some test cases have been written.
Changes have been put under SVN revision 678552
(http://svn.apache.org/viewvc?view=rev&revision=678552). This revision also
included changes to fix AXISCPP-623.
was (Author: nadiramra):
In the complex type derializer, we now doa peek at the very end to ensure
we are at the end of element.
In the stub code, after all the deserialization, a stub method call to
checkForExtraneousElements() is performed that basically does the same thing.
This has been done for doc/literal code base.
Will wait to close once some test cases have been written.
Changes have been put under SVN revision 678552
(http://svn.apache.org/viewvc?view=rev&revision=678552). This revision also
included changes to fix AXISCPP-623.
> Deserializer does give any indication of error when tags not in the WSDL are
> encountered.
> -----------------------------------------------------------------------------------------
>
> Key: AXISCPP-888
> URL: https://issues.apache.org/jira/browse/AXISCPP-888
> Project: Axis-C++
> Issue Type: Bug
> Components: Client - Deserialization
> Affects Versions: 1.5 Beta
> Environment: Linux
> Reporter: Chip Stettler
> Assignee: nadir amra
> Fix For: current (nightly)
>
>
> The WSDL contract was modified on the server to add an additional field. The
> client side marshalled all data upto the unexpected field. All data after
> the unexpected field was null, however, the call returned without error. I
> tried the same test in java Axis and java version throws 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
