[prev in list] [next in list] [prev in thread] [next in thread] 

List:       axis-c-dev
Subject:    [jira] Commented: (AXISCPP-208) SoapDeSerializer doesn't check for expected end tag, it skips next t
From:       "John Hawkins (JIRA)" <axis-c-dev () ws ! apache ! org>
Date:       2005-01-31 10:58:18
Message-ID: 1595023304.1107169098884.JavaMail.jira () ajax ! apache ! org
[Download RAW message or body]

     [ http://issues.apache.org/jira/browse/AXISCPP-208?page=comments#action_58302 ]
     
John Hawkins commented on AXISCPP-208:
--------------------------------------

did anyone put these fixes into the code ?

> SoapDeSerializer doesn't check for expected end tag, it skips next tag instead
> ------------------------------------------------------------------------------
> 
> Key: AXISCPP-208
> URL: http://issues.apache.org/jira/browse/AXISCPP-208
> Project: Axis-C++
> Type: Bug
> Components: Serialization/Deserialization
> Versions: 1.3 Beta
> Environment: HP-UX with gnu compiler
> Reporter: James Guido
> Priority: Minor
> Attachments: SoapDeSerializer.cpp.diff_with_latest_version_1.92, \
> 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:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


[prev in list] [next in list] [prev in thread] [next in thread]