Copyright 2005 Fourthought, Inc. (USA). Detailed license and copyright information: http://4suite.org/COPYRIGHT Project home, documentation, distributions: http://4suite.org/
Contains a set of XML attributes, accessible by expanded name.
This is the main callback interface for the Parser. The order of events in this interface mirrors the order of the information in the document.
The parser will call this method to report each chunk of character data. The parser will return all contiguous character data in a single chunk.
The parser will invoke this method only once, and it will be the last method invoked during the parse. The parser shall not invoke this method until it has either abandoned parsing (because of an unrecoverable error) or reached the end of input.
The uri parameter is None for elements which have no namespace, the qualifiedName parameter is the raw XML name used in the source document.
See startPrefixMapping for details. This event will always occur after the corresponding endElementNS event, but the order of endPrefixMapping events is not otherwise guaranteed.
The locator allows the application to determine the end position of any document-related event, even if the parser is not reporting an error. Typically, the application will use this information for reporting its own errors (such as character content that does not match an application's business rules). The information returned by the locator is probably not sufficient for use with a search engine. Note that the locator will return correct information only during the invocation of the events in this interface. The application should not attempt to use it at any other time.
The parser will invoke this method only once, before any other methods in this interface.
The uri parameter is None for elements which have no namespace, the qualifiedName parameter is the raw XML name used in the source document, and the atts parameter holds an instance of the Attributes class containing the attributes of the element.
The information from this event is not necessary for normal Namespace processing: the XmlParser will automatically replace prefixes for element and attribute names. There are cases, however, when applications need to use prefixes in character data or in attribute values, where they cannot safely be expanded automatically; the start/endPrefixMapping event supplies the information to the application to expand prefixes in those contexts itself, if necessary. Note that start/endPrefixMapping events are not guaranteed to be properly nested relative to each-other: all startPrefixMapping events will occur before the corresponding startElementNS event, and all endPrefixMapping events will occur after the corresponding endElementNS event, but their order is not guaranteed.