[
https://issues.apache.org/jira/browse/UIMA-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12645497#action_12645497
]
Burn Lewis commented on UIMA-1119:
----------------------------------
6 of the original 12 types of XCASParsingException are thrown from this code,
so I was simply propagating the confusion! The stack trace will show which
format is in use so perhaps we could change the messages to start with:
Error parsing XML from source {0} at line {1}, column {2}: ....
Also do we ever have the location information? I don't see any code setting
the Locator so these 3 values are always <unknown>
> The XmiCasDeserializer throws NoSuchElementException if an XCAS is corrupted,
> but doesn't report the offending element.
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: UIMA-1119
> URL: https://issues.apache.org/jira/browse/UIMA-1119
> Project: UIMA
> Issue Type: Improvement
> Components: Core Java Framework
> Affects Versions: 2.2.2
> Reporter: Burn Lewis
> Assignee: Marshall Schor
> Priority: Minor
> Attachments: UIMA-1119-3.patch
>
>
> Obviously it's dangerous to edit XCASes but it is often the quickest way to
> produce a variety of test cases for an annotator. By changing a few lines we
> can report the invalid id.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
