[UIMA-5586] uv3: DocumentAnnotation subclasses not handled as in UIMAv2 during deserialization

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0SDK-beta
• Fix Version/s: 3.0.0SDK-beta
• Component/s: Core Java Framework
• Assignee: Marshall Schor
• Reporter: Richard Eckart de Castilho
• Created: 22/Sep/17 09:13
• Updated: 25/Sep/17 16:03
• Resolved: 25/Sep/17 16:03

Description

Consider the case that you have custom subclass of the uima `DocumentAnnotation`, let's call it `DocumentMetaData`. Next, we have an XMI file which contains an annotation of the `DocumentMetaData` type.

When loading such an XMI file in UIMAv2, the CAS ends up with a single `DocumentMetaData` annotation which is accessible via `cas.getDocumentAnnotation()`.

When loading the same file with UIMAv3, the CAS ends up with both, a `DocumentAnnotation` and a `DocumentMetaData` annotation and `cas.getDocumentAnnotation()` returns the former.

The same appears to happen when deserializing a CAS from various binary formats.