[
https://issues.apache.org/jira/browse/SHINDIG-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12593596#action_12593596
]
Nik Haldimann commented on SHINDIG-219:
---------------------------------------
It appears that a Shindig XmlException can actually wrap exceptions other than
SAXParseErrors (see XmlUtil#parse)), so I'm not sure how to add line/column in
a clean way. Do you have a suggestion? In any case, I think that should be a
separate patch.
> 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.
