[
https://issues.apache.org/jira/browse/UIMA-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12649770#action_12649770
]
Adam Lally commented on UIMA-1107:
----------------------------------
Okay, I see. I've looked over the code and I don't see any better way of doing
this.
I would like to keep the ability to have the ResourceManager implementation be
parameterizable. The idea here was that if UIMA is embedded inside another
framework that has its own way of managing resources (for example, an J2EE
application server, where resources are registered in an accessed from JNDI),
the ResourceManager implementation could be substituted with one that passes
through to the container's implementation.
After considering everything I think the best approach is probably to add a new
UIMAFramework.newDefaultResourceManagerPearWrapper() as you suggested.
> Annotator context not set when annotator loaded from PEAR
> ---------------------------------------------------------
>
> Key: UIMA-1107
> URL: https://issues.apache.org/jira/browse/UIMA-1107
> Project: UIMA
> Issue Type: Bug
> Components: Core Java Framework
> Affects Versions: 2.2.2
> Reporter: Aaron Kaplan
> Assignee: Marshall Schor
> Fix For: 2.3
>
>
> I have an aggregate annotator consisting of an annotator A1 that creates a
> new sofa, and an annotator A2 that annotates the new sofa. A2 is not
> sofa-aware, so in the aggregate descriptor I have defined a sofa mapping.
> In the delegateAnalysisEngine element of the aggregate descriptor, if I point
> to A2's component descriptor (A2/desc/A2.xml), the sofa mapping works: A2
> processes the new sofa created by A1. If I point instead to A2's pear
> installation descriptor (A2/A2_pear.xml), the sofa mapping seems not to be
> applied: A2 processes the initial sofa instead.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
