Dom parser
1 like1,455 views
The document discusses two common XML parsers - DOM and SAX. DOM builds an in-memory tree representation of the entire XML document, allowing random access. SAX is event-based and parses the document sequentially, notifying the application of elements and attributes through callback methods. DOM is used when random access or rearranging elements is needed, while SAX is better for large documents or streaming data. Common DOM and SAX methods are also outlined.
Dom parser
- 2. DOM • The Document Object Model is an official recommendation of the World Wide Web Consortium (W3C). It defines an interface that enables programs to access and update the style, structure,and contents of XML documents. XML parsers that support the DOM implement that interface. • When to use? • You should use a DOM parser when: • You need to know a lot about the structure of a document • You need to move parts of the document around (you might want to sort certain elements, for example) • You need to use the information in the document more than once • What you get? • When you parse an XML document with a DOM parser, you get back a tree structure that contains all of the elements of your document. The DOM provides a variety of functions you can use to examine the contents and structure of the document.
- 4. Common DOM methods • When you are working with the DOM, there are several methods you'll use often: • Document.getDocumentElement() - Returns the root element of the document. • Node.getFirstChild() - Returns the first child of a given Node. • Node.getLastChild() - Returns the last child of a given Node. • Node.getNextSibling() - These methods return the next sibling of a given Node. • Node.getPreviousSibling() - These methods return the previous sibling of a given Node. • Node.getAttribute(attrName) - For a given Node, returns the attribute with the requested name.
- 5. Steps to Using DOM • Following are the steps used while parsing a document using DOM Parser. • Import XML-related packages. • Create a DocumentBuilder • Create a Document from a file or stream • Extract the root element • Examine attributes • Examine sub-elements • Import XML-related packages • import org.w3c.dom.*; • import javax.xml.parsers.*; • import java.io.*;
- 6. • Create a DocumentBuilder • DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance(); • DocumentBuilder builder = factory.newDocumentBuilder(); • Create a Document from a file or stream • StringBuilder xmlStringBuilder = new StringBuilder(); xmlStringBuilder.append("<?xml version="1.0"?> <class> </class>"); ByteArrayInputStream input = new ByteArrayInputStream( xmlStringBuilder.toString().getBytes("UTF-8")); • Document doc = builder.parse(input); • Extract the root element • Element root = document.getDocumentElement(); • Examine attributes • //returns specific attribute • getAttribute("attributeName"); • //returns a (table) of names/values • getAttributes(); • Examine sub-elements • //returns a list of subelements of specified name getElementsByTagName("subelementName"); / • /returns a list of all child nodes • getChildNodes();
- 12. SAX PARSER •SAX (the Simple API for XML) is an event-based parser for xml documents. • Unlike a DOM parser, a SAX parser creates no parse tree. SAX is a streaming interface for XML, which means that applications using SAX receive event notifications about the XML document being processed an element, and attribute, at a time in sequential order starting at the top of the document, and ending with the closing of the ROOT element.
- 13. SAX • Reads an XML document from top to bottom, recognizing the tokens that make up a well-formed XML document • Tokens are processed in the same order that they appear in the document • Reports the application program the nature of tokens that the parser has encountered as they occur • The application program provides an "event" handler that must be registered with the parser • As the tokens are identified, callback methods in the handler are invoked with the relevant information
- 14. When to use? • You should use a SAX parser when: • You can process the XML document in a linear fashion from the top down • The document is not deeply nested • You are processing a very large XML document whose DOM tree would consume too much memory.Typical DOM implementations use ten bytes of memory to represent one byte of XML • The problem to be solved involves only part of the XML document • Data is available as soon as it is seen by the parser, so SAX works well for an XML document that arrives over a stream • Disadvantages of SAX • We have no random access to an XML document since it is processed in a forward-only manner • If you need to keep track of data the parser has seen or change the order of items, you must write the code and store the data on your own