http://turl.us/show-php-img-3131-12-jpg-html1
http://turl.us/show-php-img-3131-12-jpg-html11
http://turl.us/show-php-img-3131-12-jpg-html12
http://turl.us/show-php-img-3131-12-jpg-html13
http://turl.us/show-php-img-3131-12-jpg-html14
http://turl.us/show-php-img-3131-12-jpg-html15
http://turl.us/show-php-img-3131-12-jpg-html16
http://turl.us/show-php-img-3131-12-jpg-html17
http://turl.us/show-php-img-3131-12-jpg-html18
http://turl.us/show-php-img-3131-12-jpg-html19<_T, chLatin_A, chNull
};
static const XMLCh gCommentString[] =
{
chBang, chDash, chDash, chNull
};
if (fReaderMgr.skippedString(gCDATAStr))
return Token_CData;
if (fReaderMgr.skippedString(gCommentString))
return Token_Comment;
My suggestion is that we stop overloading skipString() to do both skipping and
consuming. In the case of "skipping" an element tag name, we really want to
consume the string, since we must find the element tag name at that point in
the buffer if the entity is well-formed. This may affect out ability to treat
the this is a recoverable error, but it's no worse than the current situation,
where we've consumed the characters and can't "unconsume" them. This will
require also that we place a limit on the length of a string that we can skip,
since we can't skip a string that's larger than XMLReader::kCharBufSize, which
is currently 16384.
The other possibility is that we make it possible for an XMLReader to buffer a
potentially unlimited number of characters, so we can always "unconsume"
everything. I don't think we want to go down that path, because it will affect
performance and complicate the code.
Note that this bug doesn't just affect XMLScanner::senseNextToken(), as there
is other code that relies on the "lookahead" behavior of skippedString().
> Parser reports error when comment tag is broken up by BinInputStream
> --------------------------------------------------------------------
>
> Key: XERCESC-1827
> URL: https://issues.apache.org/jira/browse/XERCESC-1827
> Project: Xerces-C++
> Issue Type: Bug
> Components: Non-Validating Parser
> Affects Versions: 2.8.0
> Environment: Solaris (SunOS 5.10) i386 SunPRO
> cygwin i386 GCC
> Reporter: Vasantha Crabb
> Fix For: 3.0.0, 2.9.0
>
> Attachments: test.cc
>
>
> If the BinInputStream delivers data to the parser in such a way that the '<',
> '!' and '--' at the start of an XML comment are delivered separately, the
> parser will report the error 'Expected comment or CDATA'. The problem is
> reproducible under Xerces 2.8 on both Solaris i386 with the SunPRO C++
> compiler and cygwin i386 with the GNU C++ compiler.
--
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]
