mina-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eilon Yardeni (JIRA)" <j...@apache.org>
Subject [jira] Updated: (VYSPER-265) XMLTokenizer does not keep state across parsed IoBuffers
Date Mon, 07 Feb 2011 21:55:57 GMT

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

Eilon Yardeni updated VYSPER-265:
---------------------------------

    Attachment: tokenizer_patch.txt


The proposed attached patch fix the issue by buffering the on-going token chars, rather than
the last position in the current tokenized IoBuffer.

> XMLTokenizer does not keep state across parsed IoBuffers
> --------------------------------------------------------
>
>                 Key: VYSPER-265
>                 URL: https://issues.apache.org/jira/browse/VYSPER-265
>             Project: VYSPER
>          Issue Type: Bug
>          Components: core protocol
>    Affects Versions: 0.6
>         Environment: Using Vysper for creating XMPP client based on Java NIO.
>            Reporter: Eilon Yardeni
>              Labels: XML, parser
>             Fix For: 0.6
>
>         Attachments: tokenizer_patch.txt
>
>
> When receiving a large Stanza, some of the XML tokens
> are not parsed properly. Specifically, tag names gets broken (i.e. instead of "<item
...>" i see "<tem ...>").
> The XMLTokenizer does not keep state across two different IoBuffers that the XMLParser
is parsing during stanza decoding.
> It currently only keeps the last position in the tokenized IoBuffer, but when a new IoBuffer
is tokenized, 
> the previous partial token content is lost.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message