[
https://issues.apache.org/jira/browse/UIMA-6057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16863754#comment-16863754
]
Peter Klügl commented on UIMA-6057:
-----------------------------------
Hi,
maybe I can answer your question as I am somewhat responsible for this
requirement.
We are using several primitive analysis analysis engines that act as aggregate
analysis engine by managing other (primitive) analysis engines. I know that
this is not the correct way how to use the framework as there are aggregate
descriptions, flow controller and parameter mappings, but our use cases here go
beyond, e .g., by supporting m:n config parameter mapping. The advantages of
our approach are just so significant that we have risked future "problems".
Well, there are several, but only one serious that we cannot control the
classloader switching IFAIK which prevents the usage of pears. In my opinion,
the patch/fix is not required for the framework as it is, but it enables users
to apply the framework for some strange use cases and does not harm the common
use.
So this patch is rather important for us.
As an addition I have to mention that these problems also occur in UIMA Ruta,
as Ruta is able to initialize and execute analysis engines from within a rule
script. That's essentially the same situation.
> Avoid falsely switching classloader
> -----------------------------------
>
> Key: UIMA-6057
> URL: https://issues.apache.org/jira/browse/UIMA-6057
> Project: UIMA
> Issue Type: Bug
> 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)
