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 2017/09/18 18:50:00 UTC

[jira] [Resolved] (UIMA-5573) uv3 change JCas feature slot initialization to be more lazy

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

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

> uv3 change JCas feature slot initialization to be more lazy
> -----------------------------------------------------------
>
>                 Key: UIMA-5573
>                 URL: https://issues.apache.org/jira/browse/UIMA-5573
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Core Java Framework
>    Affects Versions: 3.0.0SDK-alpha02
>            Reporter: Marshall Schor
>            Assignee: Marshall Schor
>            Priority: Minor
>             Fix For: 3.0.0SDK-beta
>
>
> The current implementation of JCas classes requires that a type system associated with a JCas class be committed before the JCas class is loaded.  This causes some existing code to fail, because they're causing a JCas class to be loaded before the type system is committed (see UIMA-5554).  
> The reason for this design in v3 was to enable the computation of the offsets for accessing features in feature structures to be done once and saved in static final int values, for efficiency. 
> Find a new approach, which is as efficient, but is more lazy - allowing JCas classes to be loaded, and later a corresponding type system commit to be run.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)