| com.sun.xml.stream.buffer.AbstractProcessor
 com.sun.xml.stream.buffer.sax.SAXBufferProcessor
| _namespaceAttributesStack | | protected int[] _namespaceAttributesStack(Code) | | |
| _namespaceAttributesStackIndex | | protected int _namespaceAttributesStackIndex(Code) | | |
| _namespacePrefixes | | protected String[] _namespacePrefixes(Code) | | |
| _namespacePrefixesFeature | | protected boolean _namespacePrefixesFeature(Code) | | SAX Namespace attributes features
|
| _namespacePrefixesIndex | | protected int _namespacePrefixesIndex(Code) | | |
| SAXBufferProcessor | | public SAXBufferProcessor()(Code) | | |
| SAXBufferProcessor | | public SAXBufferProcessor(XMLStreamBuffer buffer, boolean produceFragmentEvent)(Code) | |
Parameters:
produceFragmentEvent - True to generate fragment SAX events without start/endDocument.False to generate a full document SAX events. |
| process | | final public void process() throws SAXException(Code) | | Parse the sub-tree (or a whole document) that
XMLStreamBuffer points to, and sends events to handlers.
TODO:
We probably need two modes for a sub-tree event generation. One for
firing a sub-tree as if it's a whole document (in which case start/endDocument
and appropriate additional namespace bindings are necessary), and the other
mode for firing a subtree as a subtree, like it does today.
A stream buffer SAX feature could be used to specify this.
throws:
SAXException - Follow the same semantics as XMLReader.parse(InputSource). |
| setXMLStreamBuffer | | public void setXMLStreamBuffer(XMLStreamBuffer buffer, boolean produceFragmentEvent)(Code) | | Resets the parser to read from the beginning of the given
XMLStreamBuffer .
Parameters:
produceFragmentEvent - True to generate fragment SAX events without start/endDocument.False to generate a full document SAX events. |
|
|