[jira] Updated: (UIMA-1107) Annotator context not set when annotator loaded from PEAR

["Eddie Epstein (JIRA)" <ui...@incubator.apache.org>]

     [ https://issues.apache.org/jira/browse/UIMA-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eddie Epstein updated UIMA-1107:
--------------------------------

    Summary: Annotator context not set when annotator loaded from PEAR  (was: Sofa mapping not applied when annotator loaded from PEAR)

Normally annotators within an aggregate share a resource manager, but annotators running in the Pear wrapper must have their own resource manager. When instantiating an annotator, the resource manager is passed in with the UIMA context object which also contains Sofa mappings and configuration parameter overrides. A redesign is needed for passing all necessary information at annotator instantiation.

> 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.