[
https://issues.apache.org/jira/browse/UIMA-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12614695#action_12614695
]
Aaron Kaplan commented on UIMA-1107:
------------------------------------
I'm not sure I understand your answer. The only place I find something called
aAdditionalParams is in Resource.initialize(), which the javadoc says
applications shouldn't call. After some digging, I think you're suggesting
that I specify the sofa mappings as in Section 6.4.4 of UIMA Tutoral and
Developers' Guides. Is that right? But I wasn't creating my aggregate
programmatically--I simply defined it in an annotator descriptor, which I
referenced in a CPE descriptor, which I instantiated using the cpeGui. Is it
impossible to specify a sofa mapping that way?
And a meta-issue: you marked this bug "Fixed" but it doesn't sound like you
changed anything. Did you mean "Invalid" or "Won't Fix?"
> 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: Eddie Epstein
>
> 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.
