You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Marshall Schor (JIRA)" <de...@uima.apache.org> on 2016/07/14 18:30:20 UTC

[jira] [Resolved] (UIMA-4823) Missing error reports for mismatch between JCas and UIMA Type system

     [ https://issues.apache.org/jira/browse/UIMA-4823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marshall Schor resolved UIMA-4823.
----------------------------------
    Resolution: Fixed

> Missing error reports for mismatch between JCas and UIMA Type system
> --------------------------------------------------------------------
>
>                 Key: UIMA-4823
>                 URL: https://issues.apache.org/jira/browse/UIMA-4823
>             Project: UIMA
>          Issue Type: Bug
>          Components: Core Java Framework
>    Affects Versions: 3.0.0SDKexp, 2.8.1SDK
>            Reporter: Marshall Schor
>            Assignee: Marshall Schor
>            Priority: Minor
>             Fix For: 2.8.2SDK
>
>
> There is a reversed boolean test in the JCasImpl method getRequiredFeatureDE, which results in never reporting feature-not-found in UIMA type system, which initializing the JCas classes.
> Fixing this causes lots of test cases to start failing, due to now exposed discrepancies between the generated JCas classes and the type system used for the test cases (which is missing some of the JCas-defined features).
> Change the reporting mechanism to allow for reporting that doesn't throw an exception (where an exception would later be thrown if a feature was accessed which isn't in the type system, anyway).  This allows existing user code which might be sharing a JCas class with "extra" defined features which are never accessed, to report this, but run anyway (if those undefined-in-the-type-system features are never attempted to be used).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)