You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org> on 2009/08/14 16:48:14 UTC
[jira] Closed: (UIMA-1318) Allow to add an
AnalysisEngineDescription to a CpeDescription
[ https://issues.apache.org/jira/browse/UIMA-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik closed UIMA-1318.
-------------------------------
Resolution: Won't Fix
Assignee: Jerry Cwiklik
The CPE already has an API to create descriptors programmatically. Check section:
"Configuring a Collection Processing Engine Descriptor Programmatically" in the UIMA Tutorial and Developers' Guides
> Allow to add an AnalysisEngineDescription to a CpeDescription
> -------------------------------------------------------------
>
> Key: UIMA-1318
> URL: https://issues.apache.org/jira/browse/UIMA-1318
> Project: UIMA
> Issue Type: Improvement
> Affects Versions: 2.2.2
> Reporter: Kai Schlamp
> Assignee: Jerry Cwiklik
>
> This would allow to build up an AnalysisEngineDesription programmatically (and so only in memory present) and use that directly in a CPE (without creating a temporary descriptor file of that description and provide that for the CPE).
> I propose methods like
> CpeComponentDescriptor.setResourceSpecifier(ResourceSpecifier rs);
> Then a an example for using it would look like this:
> AnalysisEngineDescription aeDescr = ResourceSpecifierFactory.createAnalysisEngineDescription();
> // Setup aeDescr programmatically
> CpeCasProcessor cpeProc = CpeDescriptorFactory.produceCasProcessor("CAS Proc 1");
> CPEComponentDescriptor compDescr = CpeDescriptorFactory.produceComponentDescriptor("");
> compDescr.setResourceSpecifier(aeDescr);
> cpeProc.setCpeComponentDescriptor(compDescr);
> Analog for Consumer and CollectionReader.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.