Warning: This is a facade provided for use by user code, not for implementation. User implementations of this interface are highly likely to be incompatible with future releases of the product at both binary and source levels.
An {@link XMLPipeline} is simply a useful way of organising a sequence of{@link XMLProcess}es. There is no guarantee that any two processes will actually be in the same pipeline and so processes must not rely on this. e.g. They should not use the XMLPipeline as a property key in the {@link XMLPipelineContext}.
Although it is possible neither an {@link XMLPipeline} (or{@link XMLProcess}) must be connected directly to an applications SAX event handlers, e.g. {@link org.xml.sax.ContentHandler}. The applications SAX event handlers must only be connected to either an {@link XMLPipelineReader} or an {@link XMLPipelineFilter}
Adding a process to the pipeline involves the following steps irrespective of the location in the pipeline the process is being added.
Removing a process from the pipeline involves the following steps irrespective of the location in the pipeline that the process is being added.
After removal the caller should almost certainly invoke the {@link XMLProcess#release} method to release any resources associatedwith the process.
@volantis-api-include-in PublicAPI @volantis-api-include-in ProfessionalServicesAPI @volantis-api-include-in InternalAPI
|
|
|
|
|
|
|
|