You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by "Vincent Siveton (JIRA)" <ji...@apache.org> on 2008/05/01 12:32:55 UTC

[jira] Commented: (SHINDIG-219) Improve XML parse error messages

    [ https://issues.apache.org/jira/browse/SHINDIG-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12593509#action_12593509 ] 

Vincent Siveton commented on SHINDIG-219:
-----------------------------------------

In the same vein, as SAXParseErrors has columnNumber and lineNumber, XmlException (defined in XmltUtil#parse() ) should have them too.
With this, the SpecParserException will be more precise.


> Improve XML parse error messages
> --------------------------------
>
>                 Key: SHINDIG-219
>                 URL: https://issues.apache.org/jira/browse/SHINDIG-219
>             Project: Shindig
>          Issue Type: Improvement
>          Components: Gadget Rendering Server (Java)
>            Reporter: Nik Haldimann
>            Priority: Minor
>         Attachments: improve-xml-parse-errors.patch
>
>
> On malformed gadget specs and message bundles, Shindig currently passes through SAXParseErrors which are fairly opaque. At the Shindig client level there is also no way to figure out which file (gadget spec or message bundle) is malformed.
> This patch includes the file name in the SpecParserException message which improves the situation a bit. Includes tests.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.