uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard Eckart de Castilho (JIRA)" <...@uima.apache.org>
Subject [jira] [Created] (UIMA-5297) UimaContextHolder not properly managed in pipelines
Date Mon, 06 Feb 2017 11:20:41 GMT
Richard Eckart de Castilho created UIMA-5297:
------------------------------------------------

             Summary: UimaContextHolder not properly managed in pipelines
                 Key: UIMA-5297
                 URL: https://issues.apache.org/jira/browse/UIMA-5297
             Project: UIMA
          Issue Type: Bug
          Components: uimaFIT
    Affects Versions: 2.2.0uimaFIT
            Reporter: Richard Eckart de Castilho
            Assignee: Richard Eckart de Castilho
             Fix For: 2.3.0uimaFIT


E.g. in SimplePipeline, uimaFIT manages the creation and destruction of components (readers,
engines). Because of the introduction of the UimaContextHolder in UIMA-J Core, umiaFIT now
also has to manage this.

E.g. currently in SimplePipeline

* uimaFIT instantiates a reader - which internally creates a context and calls setContext()
* uimaFIT instantiates an engine - which internally creates a context and which calls setContext()

... so reader and engine are using two different contexts and only one of them is in the holder.
This may be a problem.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message