uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marshall Schor (JIRA)" <...@uima.apache.org>
Subject [jira] [Commented] (UIMA-6057) Avoid falsely switching classloader
Date Thu, 27 Jun 2019 13:11:00 GMT

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

Marshall Schor commented on UIMA-6057:

Is this the use case:
1) start an outer uima pipeline, which establishes ClassLoader cl1.

2) configure a uimaFIT simple pipeline, which sets up ClassLoader cl2

3) run the simple-pipeline, and when it returns, you want to access its CAS using JCas classes
loaded from cl2.


But, the outer-pipeline it would seem could already have loaded JCas classes using cl1 (which
you don't want to switch back to).  Those classes would not work with the JCas classes from


So, I guess this isn't the scenario you're thinking of.  Is your scenario one where you want
the simple-pipeline to establish the class loader for the whole app to use?   (Sorry if
I'm being dense/slow, but I'd really like to understand this better, because the fix seems
like it would break a lot of things).

> 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