You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Niklas Gustavsson (JIRA)" <ji...@apache.org> on 2011/02/07 23:11:03 UTC

[jira] Closed: (VYSPER-265) XMLTokenizer does not keep state across parsed IoBuffers

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

Niklas Gustavsson closed VYSPER-265.
------------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 0.6)
                   0.7
         Assignee: Niklas Gustavsson

Committed in rev 1068168 together with a test case. Thanks for the patch!

> 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
>            Assignee: Niklas Gustavsson
>              Labels: XML, parser
>             Fix For: 0.7
>
>         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