Peter Klügl created UIMA-5730:
---------------------------------

             Summary: Using parameters of PearSpecifier for configuring wrapped 
analysis engine description
                 Key: UIMA-5730
                 URL: https://issues.apache.org/jira/browse/UIMA-5730
             Project: UIMA
          Issue Type: Improvement
          Components: Core Java Framework
    Affects Versions: 2.10.2SDK
            Reporter: Peter Klügl


The PearSpecifier provides functionality for setting parameters, which could be 
used for configuring the wrapped analysis engine description.

 

Matthias Koch wrote: 

 
{quote}I want to configure a PEAR dynamically. (I install the pear and want to 
produce the analysis engine with different parameters than in the xml). 
Is this possible? Can I use the additionalParameters? I have seen that the 
PearSpecifier has an instance variable for parameters, but no one is using 
(calling) it. 
 
I want to produce the analysisEngine with: 
UIMAFramework.produceAnalysisEngine(resourceSpecifer, resourceManager, params); 
 
In this specifier there should be one or more pearSpecifiers that should be 
configured. 
 
I have overridden the PearAnalysisEngineWrapper and built a loop that 
configures the following specifier over the configurationParameterSettings. It 
takes the parameters from the pear specifiers. 
 
line 257-258 
// Parse the resource specifier 
ResourceSpecifier specifier = 
UIMAFramework.getXMLParser().parseResourceSpecifier(in); 
 
==> added code 
AnalysisEngineDescription analysisEngineDescription = 
(AnalysisEngineDescription) specifier; 
AnalysisEngineMetaData analysisEngineMetaData = 
analysisEngineDescription.getAnalysisEngineMetaData(); 
ConfigurationParameterSettings configurationParameterSettings = 
analysisEngineMetaData.getConfigurationParameterSettings(); 
for (Parameter parameter : Arrays.asList(pearSpec.getParameters())) { 
 
configurationParameterSettings.setParameterValue(parameter.getName(), 
parameter.getValue()); 
}
{quote}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to