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 Tue, 02 Jul 2019 14:49:00 GMT

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

Marshall Schor commented on UIMA-6057:

Here's what I think the failure case is with the "block the switch-back" patch:
 * Let's say the main loaded the JCas class via some reference to it, before the special pipeline
was setup/called.
 * Let's say the PEAR classloader does *not* share the JCas classes
 * Let's say the proposed "block the switch back to the main classloader" is implemented and

Then: in the main pipeline, after the PEAR is run, an iterator getting an instance of "Foo",
would look up the JCas cover class and make an instance of "Foo"/special-pipeline-loader,
but the main class would be unable to use Foo (that it loaded with the main class loader),
and it would fail with the strange class-cast-exception.


> 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