Pipeline element
The Pipeline element defines the pipeline structure by specifying the filters and their inputs.
The Pipeline calls a filter's runFilter method, which is identified by the startFilters attribute.
In the following example, epicParser is the pipeline's source filter. The composer runs this filter when it receives the specified signal.
<Pipeline startFilters="epicParser">
|
|
If the startFilters attribute lists multiple source filters, their runFilter methods are called in the order listed.
|
The Filter element defines the filters that make up the pipeline. In the following example, the first filter in the pipeline (epicParser) is connected to the second filter (serializer) by the Input element.
<Filter id="epicParser" filterDefRef="epicGenerator">
<FilterParameter name="docId"><ComposerParameter
name="document"/></FilterParameter>
</Filter>
<Filter id="serializer" filterDefRef="fileSerializer">
<FilterParameter name="outputFile">
<ComposerParameter name="output_filename"/>
</FilterParameter>
<FilterParameter name="method">
<Value>xml</Value>
</FilterParameter>
<Input filterRef="epicParser"/>
</Filter>
Filters must receive certain parameters at run-time. These parameters can come from the composer parameters provided at run-time or they can be specified in the CCF file. For example, the serializer needs to know the name of the file to which it outputs (output_filename). The value for this parameter is provided at run-time from the composer parameter named output_filename. As a result, the value provided when the run_composer command is issued is passed to the filter.
The method parameter specifies the output format. The fileSerializer filter (Arbortext-path\composer\fileSerializer.ent) defines the valid values for the method parameter (xml, html, text, or runTime). In the following example, xml is the output method.
<FilterParameter name="method">
<Value>xml</Value>
</FilterParameter>
