You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Richard Eckart de Castilho (JIRA)" <de...@uima.apache.org> on 2019/01/14 11:33:00 UTC
[jira] [Commented] (UIMA-5957) JCasIterable and JCasIterator in
SimplePipeline should use the same ResourceManager
[ https://issues.apache.org/jira/browse/UIMA-5957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16741960#comment-16741960 ]
Richard Eckart de Castilho commented on UIMA-5957:
--------------------------------------------------
The uimaFIT pipeline runners by default always create a new resource manager unless there is an active UimaContext attached to the current thread. If this is the case, then its RM is used (see DefaultResourceManagerCreator.newResourceManager()). So either you should ensure that there is a UimaContext available or you'd need to implement your own ResourceManagerCreator.
> JCasIterable and JCasIterator in SimplePipeline should use the same ResourceManager
> -----------------------------------------------------------------------------------
>
> Key: UIMA-5957
> URL: https://issues.apache.org/jira/browse/UIMA-5957
> Project: UIMA
> Issue Type: Improvement
> Components: uimaFIT
> Affects Versions: 2.4.0uimaFIT
> Reporter: Peter Klügl
> Priority: Major
>
> Using SimplePipeline with JCas cover classes and Ruta leads currently to class loader switching for each annotator since the JCas and the annotator refer to a different uima class loader due to the resource managers. Additionally, Ruta needs to perform internal reindexing, which can lead to observed but undefined problems.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)