gnu.xml.pipeline
public interface EventConsumer
Two important categories of consumers include filters, which process events and pass them on to other consumers, and terminus (or terminal) stages, which don't pass events on. Filters are not necessarily derived from the EventFilter class, although that class can substantially simplify their construction by automating the most common activities.
Event consumers which follow certain conventions for the signatures of their constructors can be automatically assembled into pipelines by the PipelineFactory class.
Version: $Date: 2001/10/23 17:42:25 $
Method Summary | |
---|---|
ContentHandler | getContentHandler() Most stages process these core SAX callbacks. |
DTDHandler | getDTDHandler() Few stages will use unparsed entities. |
Object | getProperty(String id)
This method works like the SAX2 XMLReader method of the same name,
and is used to retrieve the optional lexical and declaration handlers
in a pipeline.
|
void | setErrorHandler(ErrorHandler handler)
This method provides a filter stage with a handler that abstracts
presentation of warnings and both recoverable and fatal errors.
|
Parameters: id This is a URI identifying the type of property desired.
Returns: The value of that property, if it is defined.
Throws: SAXNotRecognizedException Thrown if the particular pipeline stage does not understand the specified identifier.
Parameters: handler encapsulates error handling policy for this stage
Source code is under GPL (with library exception) in the JAXP project at http://www.gnu.org/software/classpathx/jaxp
This documentation was derived from that source code on 2011-08-26.