[
https://issues.apache.org/jira/browse/UIMA-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12649803#action_12649803
]
Marshall Schor commented on UIMA-1107:
--------------------------------------
To add the new newDefaultResourceManagerPearWrapper to the UIMAFramework, I
plan to do the following:
# add the newDefaultResourceManagerPearWrapper method to UIMAFramework (static
method). This method will call the _newDefaultResourceManager() method on the
"impl" of the UIMAFramework.
# Add the _newDefaultResourceManagerPearWrapper() to UIMAFramework_impl. This
loads using Class.forName a class which is obtained by parsing the
factory.config file.
# Add to the SAX parse for the factory config file, a stanza for getting the
value of a new XML element, named "resourceManagerPearWrapper", for use by the
above.
# Add an element "resourceManagerPearWrapper" to the factory.config xml,
specifying the name of the new ResourceManagerPearWrapper class.
Did I forget anything, or is this OK?
Also, I did create a test case, and verified that the fix does work, as far as
passing in the sofa mappings correctly. I'll be adding the test case to the
regression bucket. If anyone is motivated, they can add a test to see if
configuration parameters work (they should, now) going from outside the pear to
inside.
> 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.
