Mailing-List: contact dev-help@mina.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mina.apache.org
Date: Mon, 3 Jun 2013 18:25:21 +0000 (UTC)
From: "Bernd Fondermann (JIRA)" <jira@apache.org>
To: dev@mina.apache.org
Message-ID: <JIRA.12650538.1370209617143.58257.1370283921403@arcas>
In-Reply-To: <JIRA.12650538.1370209617143@arcas>
References: <JIRA.12650538.1370209617143@arcas>
Subject: [jira] [Resolved] (VYSPER-341) nbxml exception parsing multiple
 numeric character references
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Bernd Fondermann resolved VYSPER-341.
-------------------------------------

    Resolution: Fixed
    
> nbxml exception parsing multiple numeric character references
> -------------------------------------------------------------
>
>                 Key: VYSPER-341
>                 URL: https://issues.apache.org/jira/browse/VYSPER-341
>             Project: VYSPER
>          Issue Type: Bug
>          Components: extension
>            Reporter: Bernd Fondermann
>            Assignee: Bernd Fondermann
>             Fix For: 0.8
>
>
> Gene, on the mailing list:
> There is a bug in XMLParser when parsing consecutive numeric character references because UNESCAPE_UNICODE_PATTERN greedily matches.
> We found this when exchanging JSON snippets over chat. The chat client was turning the preceding whitespace in a JSON snippet into &#160;&#160;&#160;&#160; and this causes XMLParser to throw an exception trying to parse it as one character instead of as four characters.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira