[
https://issues.apache.org/jira/browse/UIMA-5586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16176748#comment-16176748
]
Marshall Schor commented on UIMA-5586:
--------------------------------------
I found a strange bug in the code that converts JCas class names to uima types
- by any chance is the type of your DocumentMetaData
"org.apache.uima.jcas.cas.DocumentMetaData" or
"org.apache.uima.jcas.tcas.DocumentMetaData"? That would encounter the bug...
Also, found out that I forgot to convert the built-in DocumentAnnotation JCas
class to the new format.
> uv3: DocumentAnnotation subclasses not handled as in UIMAv2 during
> deserialization
> ----------------------------------------------------------------------------------
>
> Key: UIMA-5586
> URL: https://issues.apache.org/jira/browse/UIMA-5586
> Project: UIMA
> Issue Type: Bug
> Components: Core Java Framework
> Affects Versions: 3.0.0SDK-beta
> Reporter: Richard Eckart de Castilho
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
