[
https://issues.apache.org/jira/browse/UIMA-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12649744#action_12649744
]
Marshall Schor commented on UIMA-1107:
--------------------------------------
I initially made it an independent class which delegates. However, that didn't
work for things where I would delegate up to the parent, which would then, in
turn, want to get something via a classpath/datapath. For instance, I think
the method registerResource makes an "initParams" map which contains a
reference to the relativePathResolver, which, in turn, needs to use the Pears'
classpath/datapath (at least in the current design).
resolveAndValidateResourceDependencies also uses the relativePathResolver. And
there are some others...
So, I would need to have copies of these methods in the new class. Using
subclassing avoids this; the new class is very small and shares more with its
parent.
> 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.
