Mailing-List: contact uima-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: uima-dev@incubator.apache.org
Message-ID: <1995885892.1223476184517.JavaMail.jira@brutus>
Date: Wed, 8 Oct 2008 07:29:44 -0700 (PDT)
From: "Aaron Kaplan (JIRA)" <uima-dev@incubator.apache.org>
To: uima-dev@incubator.apache.org
Subject: [jira] Reopened: (UIMA-1107) Sofa mapping not applied when
 annotator loaded from PEAR
In-Reply-To: <2000360658.1215604291692.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Aaron Kaplan reopened UIMA-1107:
--------------------------------


I just tested this fix for the first time, and it doesn't resolve the problem.  The symptoms are exactly as before.

> Sofa mapping not applied 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.