Inheritance diagram for Parser:
Public Methods | |
Constructors and Destructor | |
Parser () | |
virtual | ~Parser () |
The parser interfaces | |
virtual void | setEntityResolver (EntityResolver *const resolver)=0 |
virtual void | setDTDHandler (DTDHandler *const handler)=0 |
virtual void | setDocumentHandler (DocumentHandler *const handler)=0 |
virtual void | setErrorHandler (ErrorHandler *const handler)=0 |
virtual void | parse (const InputSource &source, const bool reuseGrammar=false)=0 |
virtual void | parse (const XMLCh *const systemId, const bool reuseGrammar=false)=0 |
virtual void | parse (const char *const systemId, const bool reuseGrammar=false)=0 |
All SAX parsers must implement this basic interface: it allows applications to register handlers for different types of events and to initiate a parse from a URI, or a character stream.
All SAX parsers must also implement a zero-argument constructor (though other constructors are also allowed).
SAX parsers are reusable but not re-entrant: the application may reuse a parser object (possibly with a different input source) once the first parse has completed successfully, but it may not invoke the parse() methods recursively within a parse.
DocumentHandler#DocumentHandler
HandlerBase#HandlerBase
|
The default constructor |
|
The destructor |
|
Parse an XML document from a system identifier (URI). This method is a shortcut for the common case of reading a document from a system identifier. It is the exact equivalent of the following: parse(new URLInputSource(systemId)); If the system identifier is a URL, it must be fully resolved by the application before it is passed to the parser.
Implemented in SAXParser. |
|
Parse an XML document from a system identifier (URI). This method is a shortcut for the common case of reading a document from a system identifier. It is the exact equivalent of the following: parse(new URLInputSource(systemId)); If the system identifier is a URL, it must be fully resolved by the application before it is passed to the parser.
Implemented in SAXParser. |
|
Parse an XML document. The application can use this method to instruct the SAX parser to begin parsing an XML document from any valid input source (a character stream, a byte stream, or a URI). Applications may not invoke this method while a parse is in progress (they should create a new Parser instead for each additional XML document). Once a parse is complete, an application may reuse the same Parser object, possibly with a different input source.
Implemented in SAXParser. |
|
Allow an application to register a document event handler. If the application does not register a document handler, all document events reported by the SAX parser will be silently ignored (this is the default behaviour implemented by HandlerBase). Applications may register a new or different handler in the middle of a parse, and the SAX parser must begin using the new handler immediately.
Implemented in SAXParser. |
|
Allow an application to register a DTD event handler. If the application does not register a DTD handler, all DTD events reported by the SAX parser will be silently ignored (this is the default behaviour implemented by HandlerBase). Applications may register a new or different handler in the middle of a parse, and the SAX parser must begin using the new handler immediately.
Implemented in SAXParser. |
|
Allow an application to register a custom entity resolver. If the application does not register an entity resolver, the SAX parser will resolve system identifiers and open connections to entities itself (this is the default behaviour implemented in HandlerBase). Applications may register a new or different entity resolver in the middle of a parse, and the SAX parser must begin using the new resolver immediately.
Implemented in SAXParser. |
|
Allow an application to register an error event handler. If the application does not register an error event handler, all error events reported by the SAX parser will be silently ignored, except for fatalError, which will throw a SAXException (this is the default behaviour implemented by HandlerBase). Applications may register a new or different handler in the middle of a parse, and the SAX parser must begin using the new handler immediately.
Implemented in SAXParser. |