[ 
https://issues.apache.org/jira/browse/UIMA-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12646534#action_12646534
 ] 

Marshall Schor commented on UIMA-1119:
--------------------------------------

We use the term XCAS to mean a particular serialization format in XML for an 
externalized CAS.  We don't seem to have an "official" term in our docs for the 
XMI format of the externalized CAS.  I think we need a name for this.  Can 
someone suggest something better than XMI-CAS?

The location information is a feature of the Sax Parser, and appears to be set 
- look at the callers of the method setDocumentLocator(Locator) in the 
XmiCasDeserializer.  If this isn't working, perhaps there is a simple fix.

It looks like the implementation of XMI deserialization tried to build on the 
impl of XCAS deserialization, reusing messages, etc.  As a result, the messages 
look to be misleading - they say XCAS instead of XMI-CAS, for instance.  Since 
we know which one it is, we should probably say this in the message.

We also need to add a line to the shared resource file, "xcas.properties", that 
says that despite its name (or consider changing the name), it is used for both 
XCAS and XMI-CAS messages.





> 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.

Reply via email to