[
https://issues.apache.org/jira/browse/UIMA-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis updated UIMA-1119:
-----------------------------
Attachment: UIMA-1119-3.patch
Marshall pointed out that it'd be better to create a more informative exception
rather than misuse an existing one. This 3rd patch replaces the others and
adds a new entry UNKNOWN_ID to XCASParsingException.java and xcas.properties
that generates a message of the form:
XCASParsingException: Error parsing XCAS from source <unknown> at line
<unknown>, column <unknown>: xmi id 141700 is referenced but not defined.
Note: A comment in the java code says "Automatically generated from message
catalog." but I don't know how that's done so I've included the patched code.
> 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.
