[
https://issues.apache.org/jira/browse/UIMA-6057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16877012#comment-16877012
]
Peter Klügl commented on UIMA-6057:
-----------------------------------
I would think that the situation is much simpler. In our use case it's just the
wrong class loader.
Just to clarify a few things for me:
* Is it important if "main" loaded the class before? (see last point)
* Is it necessary that the PEAR classloader shares the classes?
* Should it not also work if the same class is loaded twice since the class
loader switch will invalidate all JCas cover objects and recreate them if
necessary?
I think it's time to create a test to reproduce our problem.
> 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)
