[jira] Resolved: (AXISCPP-888) Deserializer does give any indication of error when tags not in the WSDL are encountered.

["nadir amra (JIRA)" <ax...@ws.apache.org>]

     [ https://issues.apache.org/jira/browse/AXISCPP-888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

nadir amra resolved AXISCPP-888.
--------------------------------

       Resolution: Fixed
    Fix Version/s: current (nightly)

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.



> 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: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org