[
https://issues.apache.org/jira/browse/UIMA-6057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16873912#comment-16873912
]
Richard Eckart de Castilho commented on UIMA-6057:
--------------------------------------------------
I just had a look at SimplePipeline.iteratePipeline in 2.5.0-SNAPSHOT and as
far as I can tell, the same resource manager should be used for the CAS, reader
and all engines:
* SimplePipeline.iteratePipeline delegates to JCasIterable
* JCasIterable.iterator() creates a ResourceManager using the current
ResourceManagerFactory and then uses it to instantiate the CollectionReader as
well as an aggregate analysis engine which contains the other pipeline
components
* ... then JCasIterable.iterator() delegates to JCasIterator passing the
ResourceManager on to it
* JCasIterator then creates the JCas using the given ResourceManager
So... as far as I can see, the issue that we had should be fixed here.
In uimaFIT 2.4.0, the ResourceManager is however *not* passed on to
JCasIterator, causing the JCas to use a different ResourceManager than the
pipeline.
So your problem should be fixed by switching to uimaFIT 2.5.0-SNAPSHOT. I guess
it would be a good idea to make a uimaFIT 2.5.0 release then...
> Avoid falsely switching classloader
> -----------------------------------
>
> Key: UIMA-6057
> URL: https://issues.apache.org/jira/browse/UIMA-6057
> Project: UIMA
> Issue Type: Bug
> Components: Core Java Framework
> Reporter: Matthias Koch
> Priority: Major
> Attachments: UIMA-6057.diff
>
>
> In some cases the classloader is switched back, although it hasn't be
> switched before processing.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
