uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Klügl (JIRA) <...@uima.apache.org>
Subject [jira] [Commented] (UIMA-6057) Avoid falsely switching classloader
Date Thu, 27 Jun 2019 07:25:00 GMT

    [ https://issues.apache.org/jira/browse/UIMA-6057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16873881#comment-16873881

Peter Klügl commented on UIMA-6057:

For SimplePipeline.iteratePipeline(), you get a different UIMA wrapper class loader if the
ResourceManagerCreator is not set in ResourceManagerFactory. The factory for the jcas and
the analysis engine create each a new resource manager which creates the separate UIMA class
loader. Then, the instance comparison fails and causes the switching. This can be avoided
by setting the creator or in not using uimaFIT. I think I already discussed the siutation
with Richard a few months ago.

However, it would be really helpful to have this additional boolean switch anyways. It is
a show stopper for us.

> 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

This message was sent by Atlassian JIRA

View raw message