See: Description
Class | Description |
---|---|
AggregateBuilder |
This builder makes it easier to create an aggregate analysis engine.
|
AnalysisEngineFactory |
A collection of static methods for creating UIMA
AnalysisEngineDescriptions and AnalysisEngines . |
AnnotationFactory |
Convenience methods to create annotations
|
CapabilityFactory | |
CasFactory |
Convenience methods to create
CAS objects. |
CollectionReaderFactory | |
ConfigurationParameterFactory | |
ConfigurationParameterFactory.ConfigurationData |
A simple class for storing an array of configuration parameters along with an array of the
values that will fill in those configuration parameters
|
ExternalResourceFactory |
Helper methods for external resources.
|
FlowControllerFactory | |
FsIndexFactory | |
JCasBuilder |
Allows to add types and text to a CAS easily piece by piece.
|
JCasFactory |
Convenience methods to create
JCas objects. |
ResourceCreationSpecifierFactory | |
ResourceMetaDataFactory |
Convenience methods to create resource metadata.
|
SofaMappingFactory |
Convenience methods to handle SofA mappings.
|
TypePrioritiesFactory | |
TypeSystemDescriptionFactory | |
UimaContextFactory |
SimplePipeline
or
within a Collection Processing Engine, the pipeline logic takes care of invoking the life-cycle
methods on a component, such as:
UimaContext
with the desired parametrization of the component.
Not letting UIMA/uimaFIT manage the life-cycle of a component can, thus, have some unexpected
effects. For example, a CollectionReader
cannot be reused
after it has been passed to a SimplePipeline.runPipeline(org.apache.uima.collection.CollectionReader, org.apache.uima.analysis_engine.AnalysisEngine...)
.
The pipeline reads all files from the reader instance, and when it is complete, the reader does
not have any more data to produce. Passing the reader to subsequent runPipeline
methods will not
produce any results. When a CollectionReaderDescription
is passed instead, the reader is created, initalized, and destroyed inside the
runPipeline
method. The description can be passed to multiple runPipeline
calls
and each time, it will behave the same way, producing all its data.Copyright © 2012–2021 The Apache Software Foundation. All rights reserved.