axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From axis-c-...@ws.apache.org
Subject [jira] Commented: (AXISCPP-208) SoapDeSerializer doesn't check for expected end tag, it skips next tag instead
Date Wed, 20 Oct 2004 02:04:51 GMT
The following comment has been added to this issue:

     Author: Samisa Abeysinghe
    Created: Tue, 19 Oct 2004 7:04 PM
       Body:
If there is an error in the middle of the XML strem, with the pull model, I do not see the
value of validating the end tag, bacase after all the expected format is not there and it
is going to fail anyway. So why not indicate the error early than late?
---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/AXISCPP-208?page=comments#action_54369

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/AXISCPP-208

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXISCPP-208
    Summary: SoapDeSerializer doesn't check for expected end tag, it skips next tag instead
       Type: Bug

     Status: Unassigned
   Priority: Minor

    Project: Axis-C++
 Components: 
             Serialization/Deserialization
   Versions:
             1.3 Beta

   Assignee: 
   Reporter: James Guido

    Created: Mon, 18 Oct 2004 12:47 PM
    Updated: Tue, 19 Oct 2004 7:04 PM
Environment: HP-UX with gnu compiler

Description:
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).


---------------------------------------------------------------------
JIRA INFORMATION:
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


Mime
View raw message