Eddie,
(Baptiste's problem and mine are the same--we're working together.)
I tried your first example and I can't even get that to work using the
pear descriptor and the trunk version of uima-core. No need to go to
the second, more complicated version with two annotators and three
views. The aggregate descriptor I wrote when following your test case
instructions is below. Do you see anything wrong?
I put a breakpoint at the line in PearAnalysisEngineWrapper.java where
produceAnalysisEngine() is called. The breakpoint is reached twice, and
the argument clonedAdditionalParameters has the following values:
First time:
{PARAM_AGGREGATE_ANALYSIS_ENGINE_NAME=Aggregate,
CONFIG_PARAM_SETTINGS=org.apache.uima.resource.metadata.impl.ConfigurationParameterSettings_impl:
parameterSettings = Array{}
settingsForGroups = {}
}
Second time:
{PARAM_AGGREGATE_ANALYSIS_ENGINE_NAME=Aggregate,
[EMAIL PROTECTED],
CONFIG_PARAM_SETTINGS=org.apache.uima.resource.metadata.impl.ConfigurationParameterSettings_impl:
parameterSettings = Array{}
settingsForGroups = {}
}
-Aaron
<?xml version="1.0" encoding="UTF-8"?>
<analysisEngineDescription xmlns="http://uima.apache.org/resourceSpecifier";>
<frameworkImplementation>org.apache.uima.java</frameworkImplementation>
<primitive>false</primitive>
<delegateAnalysisEngineSpecifiers>
<delegateAnalysisEngine key="SofaExampleAnnotator">
<import
location="/home/akaplan/uima/installtest/1107test/1107test_pear.xml"/>
</delegateAnalysisEngine>
</delegateAnalysisEngineSpecifiers>
<analysisEngineMetaData>
<name>Aggregate</name>
<description/>
<version>1.0</version>
<vendor/>
<configurationParameters/>
<configurationParameterSettings/>
<flowConstraints>
<fixedFlow>
<node>SofaExampleAnnotator</node>
</fixedFlow>
</flowConstraints>
<fsIndexCollection/>
<capabilities>
<capability>
<inputs/>
<outputs/>
<inputSofas>
<sofaName>_InitialView</sofaName>
</inputSofas>
<outputSofas>
<sofaName>GermanView</sofaName>
</outputSofas>
<languagesSupported/>
</capability>
</capabilities>
<operationalProperties>
<modifiesCas>true</modifiesCas>
<multipleDeploymentAllowed>true</multipleDeploymentAllowed>
<outputsNewCASes>false</outputsNewCASes>
</operationalProperties>
</analysisEngineMetaData>
<resourceManagerConfiguration/>
<sofaMappings>
<sofaMapping>
<componentKey>SofaExampleAnnotator</componentKey>
<componentSofaName>EnglishDocument</componentSofaName>
<aggregateSofaName>_InitialView</aggregateSofaName>
</sofaMapping>
<sofaMapping>
<componentKey>SofaExampleAnnotator</componentKey>
<componentSofaName>GermanDocument</componentSofaName>
<aggregateSofaName>GermanView</aggregateSofaName>
</sofaMapping>
</sofaMappings>
</analysisEngineDescription>
Eddie Epstein wrote:
Hi Baptiste,
I'm having a problem recreating the problem. Maybe I don't understand the
scenario correctly. Here's what I did initially to debug the problem:
1. create an eclipse workspace with the uimaj-examples project.
2. create a second project with just the SofaExampleAnnotator source
and descriptor.
3. Create a pear file with the SofaExampleAnnotator source and descriptor
4. create an aggregate descriptor in the new project that wraps either the
SofaExampleAnnotator or the pear file, and declares Sofa mapping
to map _InitialView into EnglishDocument
5. run the aggregate using CVD
Using the 2.2.2 release, the aggregate wrapping SofaExampleAnnotator works,
but it fails when wrapping the pear file.
To fix the pear problem, I imported uimaj-core as a new project in the workspace
and modified the code (1107 fix). Then, I modified the CVD run configuration to
include the uimaj-core project in the front. This worked, and continues to work
for me using the latest uimaj-core from the trunk.
