Examples of XmlDocumentBuilder

com.sun.xml.tree.XmlDocumentBuilder
This class is a SAX DocumentHandler which converts a stream of parse events into an in-memory DOM document. After each Parser.parse() invocation returns, a resulting DOM Document may be accessed via the getDocument method. The parser and its builder should be used together; the builder may be used with only one parser at a time.
This builder optionally does XML namespace processing, reporting conformance problems as recoverable errors using the parser's error handler. If the parser is not a Sun parser, that handler will be inaccessible and so such errors will always be fatal. Also, if that handler does not treat such errors as fatal, processing will continue without raising an exception.
To customize the document, a powerful technique involves using an element factory specifying what element tags (from a given XML namespace) correspond to what implementation classes. Parse trees produced by such a builder can have nodes which add behaviors to achieve application-specific functionality, such as modifing the tree as it is parsed.
The object model here is that XML elements are polymorphic, with semantic intelligence embedded through customized internal nodes. Those nodes are created as the parse tree is built. Such trees now build on the W3C Document Object Model (DOM), and other models may be supported by the customized nodes. This allows both generic tools (understanding generic interfaces such as the DOM core) and specialized tools (supporting specialized behaviors, such as the HTML extensions to the DOM core; or for XSL elements) to share data structures.
Normally only "model" semantics are in document data structures, but "view" or "controller" semantics can be supported if desired.
Elements may choose to intercept certain parsing events directly. They do this by overriding the default implementations of methods in the XmlReadable interface. This is normally done to make the DOM tree represent application level modeling requirements, rather than matching an XML structure that may not be optimized appropriately. @author David Brownell @version $Revision: 1.7 $
net.sourceforge.jivalo.xmlparser.tree.XmlDocumentBuilder
This class is a SAX2 ContentHandler which converts a stream of parse events into an in-memory DOM document. After each Parser.parse() invocation returns, a resulting DOM Document may be accessed via the getDocument method. The parser and its builder should be used together; the builder may be used with only one parser at a time.
This builder optionally does XML namespace processing, reporting conformance problems as recoverable errors using the parser's error handler.
Note: element factories are deprecated because they are non-standard and are provided here only for backwards compatibility. To customize the document, a powerful technique involves using an element factory specifying what element tags (from a given XML namespace) correspond to what implementation classes. Parse trees produced by such a builder can have nodes which add behaviors to achieve application-specific functionality, such as modifing the tree as it is parsed.
The object model here is that XML elements are polymorphic, with semantic intelligence embedded through customized internal nodes. Those nodes are created as the parse tree is built. Such trees now build on the W3C Document Object Model (DOM), and other models may be supported by the customized nodes. This allows both generic tools (understanding generic interfaces such as the DOM core) and specialized tools (supporting specialized behaviors, such as the HTML extensions to the DOM core; or for XSL elements) to share data structures.
Normally only "model" semantics are in document data structures, but "view" or "controller" semantics can be supported if desired.
Elements may choose to intercept certain parsing events directly. They do this by overriding the default implementations of methods in the XmlReadable interface. This is normally done to make the DOM tree represent application level modeling requirements, rather than matching an XML structure that may not be optimized appropriately. @author David Brownell @version $Revision: 1.6 $
org.apache.crimson.tree.XmlDocumentBuilder
This class is a SAX2 ContentHandler which converts a stream of parse events into an in-memory DOM document. After each Parser.parse() invocation returns, a resulting DOM Document may be accessed via the getDocument method. The parser and its builder should be used together; the builder may be used with only one parser at a time.
This builder optionally does XML namespace processing, reporting conformance problems as recoverable errors using the parser's error handler.
Note: element factories are deprecated because they are non-standard and are provided here only for backwards compatibility. To customize the document, a powerful technique involves using an element factory specifying what element tags (from a given XML namespace) correspond to what implementation classes. Parse trees produced by such a builder can have nodes which add behaviors to achieve application-specific functionality, such as modifing the tree as it is parsed.
The object model here is that XML elements are polymorphic, with semantic intelligence embedded through customized internal nodes. Those nodes are created as the parse tree is built. Such trees now build on the W3C Document Object Model (DOM), and other models may be supported by the customized nodes. This allows both generic tools (understanding generic interfaces such as the DOM core) and specialized tools (supporting specialized behaviors, such as the HTML extensions to the DOM core; or for XSL elements) to share data structures.
Normally only "model" semantics are in document data structures, but "view" or "controller" semantics can be supported if desired.
Elements may choose to intercept certain parsing events directly. They do this by overriding the default implementations of methods in the XmlReadable interface. This is normally done to make the DOM tree represent application level modeling requirements, rather than matching an XML structure that may not be optimized appropriately. @author David Brownell @version $Revision: 1.6 $

Examples of org.apache.crimson.tree.XmlDocumentBuilder


            // Use the appropriate DOM builder based on "namespaceAware"
            if (namespaceAware) {
                builder = new XmlDocumentBuilderNS();
            } else {
                builder = new XmlDocumentBuilder();
            }


            // Use builder as the ContentHandler
            xmlReader.setContentHandler(builder);

View Full Code Here

0 1

TOP

All source code are property of their respective owners. Java is a trademark of Sun Microsystems, Inc and owned by ORACLE Inc. Contact coftware#gmail.com.