Detailed explanation of XML SAX parsing
The final function of DOM and SAX is to allow us to use languages such as java JavaScript to obtain nodes, text, attributes and other information in xml files.
This article is quoted from other blogs. The content is easy to understand. In order to save time, I have directly excerpted it. There are usually two ways to parse XML in JAVA, DOM and SAX. Although DOM is a W3C standard and provides a standard parsing method, its parsing efficiency has always been unsatisfactory, because when using DOM to parse XML, the parser reads the entire document and builds a memory-resident tree structure (node tree). ), and then your code can use the DOM's standard interface to manipulate the tree structure. But in most cases we are only interested in part of the document, without parsing the entire document first, and it is also very time-consuming to index some of the data we need from the root node of the node tree.
SAX is an alternative to XML parsing. Compared to the Document Object Model DOM, SAX is a faster and lighter way to read and manipulate XML data
#. SAX allows you to process a document as it is read, so you don't have to wait for the entire document to be stored before taking action. It doesn't involve the overhead and conceptual leaps necessary for the DOM. SAX API is an event-based API suitable for processing data streams, that is, processing data sequentially as the data flows. The SAX API
# will notify you when certain events occur while it is parsing your document. Data you do not save will be discarded when you respond to it.
The following is an example of SAX parsing XML (a bit long, because all methods of SAX event processing are annotated in detail). There are four main interfaces for processing events in the SAX API. , they are ContentHandler, DTDHandler, EntityResolver and ErrorHandler respectively. The following example may be a bit lengthy. In fact, as long as you inherit the DefaultHandler class and overwrite some of the event processing methods, you can also achieve the effect of this example. But in order to have an overview, let's take a look at all the main event parsing methods in the SAX API. (In fact, DefaultHandler implements the above four event handler interfaces, and then provides the default implementation of each abstract method.)
1, ContentHandler interface: receiving documents Handler interface for notifications of logical content.
Java Code Collection Code
'import org.xml.sax.Attributes;
import org.xml.sax.ContentHandler;
import org. xml.sax.Locator;
import org.xml.sax.SAXException;
class MyContentHandler implements ContentHandler{
StringBuffer jsonStringBuffer;
int frontBlankCount = 0;
public MyContentHandler(){
jsonStringBuffer = new StringBuffer();
}
/*
* Receive notification of character data.
* In the DOM, ch[begin:end] is equivalent to the node value of the Text node (nodeValue)
*/
@Override
public void characters(char[] ch, int begin, int length) throws SAXException {
StringBuffer buffer = new StringBuffer();
for(int i = begin; i < begin+length; i++){
switch(ch[i]){
case '\\\\\\\\\\\\\\\\\\\\\\\\ \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ \\\':buffer.append("\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ \\\\\\\\\\\\\\\");break;
case '\\\\\\\\\\\\\\\\\\\\ \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\r':buffer.append( "\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ \\\\\\\\\\\\\\\\\\\\\\\\\\\\r");break;
case '\\\\\\\ \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ \\\\\\\n':buffer.append("\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\n");break;
case '\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ \\\\\\\\\\\\\\\\\\\\\t':buffer.append("\\\\\\\\\\\\\\\\\\\ \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ \\\\\\\t");break;
case '\\\\\\\\\\\\\\\\\\\\\\\\\\\ \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\"':buffer.append("\\\\\\\ \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\"");break;
default : buffer .append(ch[i]);
}
}
System.out.println(this.toBlankString(this.frontBlankCount)+
">>> characters("+length+"): "+buffer.toString());
}
/*
* Receive notification of the end of the document.
*/
@Override
public void endDocument() throws SAXException {
System.out.println(this.toBlankString(--this. frontBlankCount)+
">>> end document");
}
}}System.out.println(this.toBlankString(this.frontBlankCount)+">>> ignorable whitespace("+length+"): "+ buffer.toString());}
##}
/*
* Receive notification of skipped entities.
* The meaning of the parameters is as follows:
* name: The name of the entity to be skipped. If it is a parameter entity, the name will start with '%',
* If it is an external DTD subset, it will be the string "[dtd]"
*/
@Override
public void skippedEntity(String name ) throws SAXException {
System.out.println(this.toBlankString(this.frontBlankCount)+
">>> skipped_entity : "+name);
}
/*
* Receive notification of the start of a document.
*/
@Override
public void startDocument() throws SAXException {
System.out.println(this.toBlankString(this.frontBlankCount++) +
">>> start document ");
}
/*
* Receive notification of the start of an element.
* The meaning of the parameters is as follows:
* uri: the namespace of the element
* localName: the local name of the element (without prefix)
* qName : Qualified name of the element (with prefix)
* atts : Attribute collection of the element
*/
@Override
public void startElement(String uri , String localName, String qName,
Attributes atts) throws SAXException {
System.out.println(this.toBlankString(this.frontBlankCount++)+
">> ;> start element : "+qName+"("+uri+")");
}
/*
* Start prefix URI namespace scope mapping.
* The information for this event is not necessary for normal namespace processing:
* When the http://xml.org/sax/features/namespaces feature is true (default),
* The SAX XML reader will automatically replace prefixes in element and attribute names.
* Parameter meanings are as follows:
* prefix: prefix
* uri: namespace
*/
@Override
public void startPrefixMapping(String prefix,String uri)
throws SAXException {
System.out.println(this.toBlankString(this.frontBlankCount++)+
">>> start prefix_mapping : xmlns:"+prefix+" = "
+"\\\\\\\\\\\\\\\\\\\\\\\ \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\""+uri+"\\\\\ \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ \\\\\\\\\"");
}
private String toBlankString(int count ){
StringBuffer buffer = new StringBuffer();
for(int i = 0;i
buffer.append(" ");
return buffer.toString();
}
}'
2, DDTHandler interface: processor interface that receives notifications of DTD-related events
Java code collection code
'import org.xml.sax.DTDHandler;
import org.xml.sax.SAXException;
String notationName) throws SAXException {System.out.println(">>> unparsed entity declare : (name = "+name+",systemId = " +publicId+",publicId = "+systemId+",notationName = "+notationName+")");}
##import org.xml.sax.EntityResolver;
import org.xml.sax.InputSource;
import org.xml.sax.SAXException;
##public class MyEntityResolver implements EntityResolver {
/*
* Returns:
* An InputSource object describing the new input source, or null,
* to request the parser to open a regular URI connection to the system identifier.
*/
@Override
public InputSource resolveEntity(String publicId, String systemId)
throws SAXException, IOException {
return null;
}
}
##public class MyErrorHandler implements ErrorHandler {
/*
* Receive notification of recoverable errors
*/
@Override
public void error(SAXParseException e) throws SAXException {
System.err.println ("Error ("+e.getLineNumber()+","
+e.getColumnNumber()+") : "+e.getMessage());
}
/*
* Receive notification of unrecoverable errors.
*/
@Override
public void fatalError(SAXParseException e) throws SAXException {
System.err.println("FatalError ("+e .getLineNumber()+","
+e.getColumnNumber()+") : "+e.getMessage());
}
/*
* Receive notification of unrecoverable errors.
*/
@Override
public void warning(SAXParseException e) throws SAXException {
System.err.println("Warning ("+e .getLineNumber()+","
+e.getColumnNumber()+") : "+e.getMessage());
}
}
The main method of the Test class prints event information when parsing books.xml.
Java Code Collection Code
import java.io.FileNotFoundException;
import java.io.FileReader;
import java.io.IOException;
import org.xml.sax.ContentHandler;
import org.xml.sax.DTDHandler;
import org.xml.sax .EntityResolver;
import org.xml.sax.ErrorHandler;
import org.xml.sax.InputSource;
import org.xml.sax.SAXException;
import org.xml.sax.XMLReader;
import org.xml.sax.helpers.XMLReaderFactory;
##public class Test {
public static void main(String[] args) throws SAXException,
EntityResolver entityResolver = new MyEntityResolver();
//Create an XML parser (read and parse XML through SAX)
//Set the XML parser's handler for handling document content-related eventsreader.setContentHandler(contentHandler);//Set the XML parser's handler for handling error eventsreader.setErrorHandler(errorHandler);//Set the handler of the XML parser to handle DTD related eventsreader.setDTDHandler(dtdHandler);//Set the entity parser of the XML parserreader.setEntityResolver(entityResolver);//Parse the books.xml documentreader.parse(new InputSource( new FileReader("books.xml")));} ##}'
##Thinking in JAVA
##Core JAVA2
C++ primer
##>>> set document_locator: (lineNumber = 1, columnNumber = 1, systemId = null, publicId = null)
Error (2,7) : Document root element "books", must match DOCTYPE root "null".
>>> start prefix_mapping : xmlns: = "http://test.org/books"
> >> start element : books(http://test.org/books)
>>> characters(2): \\\\\\\\\\\\\\ \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ n\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ \\\\\\\\\\\\\\t
>>> characters(2): \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\n\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\t
>>> start element : book(http://test.org/books)
>>> characters(3): \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\n\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\t\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\t
>>> start element : name(http://test.org/books)
>>> characters(16): Thinking in JAVA
>>> end element : name(http://test.org/books)
>>> characters(2): \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\n\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\t
>>> end element : book(http://test.org/books)
>>> characters(2): \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\n\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\t
>>> start element : book(http://test.org/books)
>>> characters(3): \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\n\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\t\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\t
>>> start element : name(http://test.org/books)
>>> characters(10): Core JAVA2
>>> end element : name(http://test.org/books)
>>> characters(2): \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\n\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\t
>>> end element : book(http://test.org/books)
>>> characters(2): \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\n\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\t
>>> start element : book(http://test.org/books)
>>> characters(3): \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\n\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\t\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\t
>>> start element : name(http://test.org/books)
>>> characters(10): C++ primer
>>> end element : name(http://test.org/books)
>>> characters(2): \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\n\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\t
>>> end element : book(http://test.org/books)
>>> characters(1): \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\n
>>> end element : books(http://test.org/books)
>>> end prefix_mapping :
>>> end document
The above is the detailed content of Detailed explanation of XML SAX parsing. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



The speed of mobile XML to PDF depends on the following factors: the complexity of XML structure. Mobile hardware configuration conversion method (library, algorithm) code quality optimization methods (select efficient libraries, optimize algorithms, cache data, and utilize multi-threading). Overall, there is no absolute answer and it needs to be optimized according to the specific situation.

It is impossible to complete XML to PDF conversion directly on your phone with a single application. It is necessary to use cloud services, which can be achieved through two steps: 1. Convert XML to PDF in the cloud, 2. Access or download the converted PDF file on the mobile phone.

It is not easy to convert XML to PDF directly on your phone, but it can be achieved with the help of cloud services. It is recommended to use a lightweight mobile app to upload XML files and receive generated PDFs, and convert them with cloud APIs. Cloud APIs use serverless computing services, and choosing the right platform is crucial. Complexity, error handling, security, and optimization strategies need to be considered when handling XML parsing and PDF generation. The entire process requires the front-end app and the back-end API to work together, and it requires some understanding of a variety of technologies.

To open a web.xml file, you can use the following methods: Use a text editor (such as Notepad or TextEdit) to edit commands using an integrated development environment (such as Eclipse or NetBeans) (Windows: notepad web.xml; Mac/Linux: open -a TextEdit web.xml)

XML formatting tools can type code according to rules to improve readability and understanding. When selecting a tool, pay attention to customization capabilities, handling of special circumstances, performance and ease of use. Commonly used tool types include online tools, IDE plug-ins, and command-line tools.

An application that converts XML directly to PDF cannot be found because they are two fundamentally different formats. XML is used to store data, while PDF is used to display documents. To complete the transformation, you can use programming languages and libraries such as Python and ReportLab to parse XML data and generate PDF documents.

Use most text editors to open XML files; if you need a more intuitive tree display, you can use an XML editor, such as Oxygen XML Editor or XMLSpy; if you process XML data in a program, you need to use a programming language (such as Python) and XML libraries (such as xml.etree.ElementTree) to parse.

XML Online Format Tools automatically organizes messy XML code into easy-to-read and maintain formats. By parsing the syntax tree of XML and applying formatting rules, these tools optimize the structure of the code, enhancing its maintainability and teamwork efficiency.
