axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fred Preston (JIRA)" <>
Subject [jira] Closed: (AXISCPP-208) SoapDeSerializer doesn't check for expected end tag, it skips next tag instead
Date Wed, 05 Apr 2006 13:05:29 GMT
     [ ]
Fred Preston closed AXISCPP-208:

> SoapDeSerializer doesn't check for expected end tag, it skips next tag instead
> ------------------------------------------------------------------------------
>          Key: AXISCPP-208
>          URL:
>      Project: Axis-C++
>         Type: Bug

>   Components: Serialization, Server - Apache module
>     Versions: 1.3 Beta
>  Environment: HP-UX with gnu compiler
>     Reporter: James Guido
>     Assignee: Adrian Dick
>     Priority: Minor
>      Fix For: 1.5 Final
>  Attachments: SoapDeSerializer.cpp.diff_with_latest_version_1.92, SoapDeSerializer.cpp.diff_with_latest_version_1.92,
> Current code blindly skips next tag, when supposedly skipping end tag.
> Case scenario:
> If client and server have a mismatch such as an extra tag was added to client, but not
yet to server. Server stops parsing due to unknown tag, and ignores all following tags. Server
gets half of the data, instead of error'ng. This is a very undesirable behavior.
> I'm posting a fix/change, where SoapDeSerializer checks for an end tag and the right
tag name before skipping tag. If tag is not an ending tag or it does not have the right tag
name, it errors.
> I have only changed getCmplxObject and getCmplxArray for DOC_ENCODING.
> Changes to the RPC_ENCODING code may also be desired.
> Blindly skipping ending tags may be a desired performance improvement for simple tags
(no nested tags).

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message