Home > Articles > Web Services > XML

📄 Contents

  1. Sams Teach Yourself XML in 21 Days, Third Edition
  2. Table of Contents
  3. About the Author
  4. Acknowledgments
  5. We Want to Hear from You!
  6. Introduction
  7. Part I: At a Glance
  8. Day 1. Welcome to XML
  9. All About Markup Languages
  10. All About XML
  11. Looking at XML in a Browser
  12. Working with XML Data Yourself
  13. Structuring Your Data
  14. Creating Well-Formed XML Documents
  15. Creating Valid XML Documents
  16. How XML Is Used in the Real World
  17. Online XML Resources
  18. Summary
  19. Q&A
  20. Workshop
  21. Day 2. Creating XML Documents
  22. Choosing an XML Editor
  23. Using XML Browsers
  24. Using XML Validators
  25. Creating XML Documents Piece by Piece
  26. Creating Prologs
  27. Creating an XML Declaration
  28. Creating XML Comments
  29. Creating Processing Instructions
  30. Creating Tags and Elements
  31. Creating CDATA Sections
  32. Handling Entities
  33. Summary
  34. Q&A
  35. Workshop
  36. Day 3. Creating Well-Formed XML Documents
  37. What Makes an XML Document Well-Formed?
  38. Creating an Example XML Document
  39. Understanding the Well-Formedness Constraints
  40. Using XML Namespaces
  41. Understanding XML Infosets
  42. Understanding Canonical XML
  43. Summary
  44. Q&A
  45. Workshop
  46. Day 4. Creating Valid XML Documents: DTDs
  47. All About DTDs
  48. Validating a Document by Using a DTD
  49. Creating Element Content Models
  50. Commenting a DTD
  51. Supporting External DTDs
  52. Handling Namespaces in DTDs
  53. Summary
  54. Q&A
  55. Workshop
  56. Declaring Attributes in DTDs
  57. Day 5. Handling Attributes and Entities in DTDs
  58. Specifying Default Values
  59. Specifying Attribute Types
  60. Handling Entities
  61. Summary
  62. Q&A
  63. Workshop
  64. Day 6. Creating Valid XML Documents: XML Schemas
  65. Using XML Schema Tools
  66. Creating XML Schemas
  67. Dissecting an XML Schema
  68. The Built-in XML Schema Elements
  69. Creating Elements and Types
  70. Specifying a Number of Elements
  71. Specifying Element Default Values
  72. Creating Attributes
  73. Summary
  74. Q&A
  75. Workshop
  76. Day 7. Creating Types in XML Schemas
  77. Restricting Simple Types by Using XML Schema Facets
  78. Creating XML Schema Choices
  79. Using Anonymous Type Definitions
  80. Declaring Empty Elements
  81. Declaring Mixed-Content Elements
  82. Grouping Elements Together
  83. Grouping Attributes Together
  84. Declaring all Groups
  85. Handling Namespaces in Schemas
  86. Annotating an XML Schema
  87. Summary
  88. Q&A
  89. Workshop
  90. Part I. In Review
  91. Well-Formed Documents
  92. Valid Documents
  93. Part II: At a Glance
  94. Day 8. Formatting XML by Using Cascading Style Sheets
  95. Our Sample XML Document
  96. Introducing CSS
  97. Connecting CSS Style Sheets and XML Documents
  98. Creating Style Sheet Selectors
  99. Using Inline Styles
  100. Creating Style Rule Specifications in Style Sheets
  101. Summary
  102. Q&A
  103. Workshop
  104. Day 9. Formatting XML by Using XSLT
  105. Introducing XSLT
  106. Transforming XML by Using XSLT
  107. Writing XSLT Style Sheets
  108. Using <xsl:apply-templates>
  109. Using <xsl:value-of> and <xsl:for-each>
  110. Matching Nodes by Using the match Attribute
  111. Working with the select Attribute and XPath
  112. Using <xsl:copy>
  113. Using <xsl:if>
  114. Using <xsl:choose>
  115. Specifying the Output Document Type
  116. Summary
  117. Q&A
  118. Workshop
  119. Day 10. Working with XSL Formatting Objects
  120. Introducing XSL-FO
  121. Using XSL-FO
  122. Using XSL Formatting Objects and Properties
  123. Building an XSL-FO Document
  124. Handling Inline Formatting
  125. Formatting Lists
  126. Formatting Tables
  127. Summary
  128. Q&A
  129. Workshop
  130. Part II. In Review
  131. Using CSS
  132. Using XSLT
  133. Using XSL-FO
  134. Part III: At a Glance
  135. Day 11. Extending HTML with XHTML
  136. Why XHTML?
  137. Writing XHTML Documents
  138. Validating XHTML Documents
  139. The Basic XHTML Elements
  140. Organizing Text
  141. Formatting Text
  142. Selecting Fonts: <font>
  143. Comments: <!-->
  144. Summary
  145. Q&A
  146. Workshop
  147. Day 12. Putting XHTML to Work
  148. Creating Hyperlinks: <a>
  149. Linking to Other Documents: <link>
  150. Handling Images: <img>
  151. Creating Frame Documents: <frameset>
  152. Creating Frames: <frame>
  153. Creating Embedded Style Sheets: <style>
  154. Formatting Tables: <table>
  155. Creating Table Rows: <tr>
  156. Formatting Table Headers: <th>
  157. Formatting Table Data: <td>
  158. Extending XHTML
  159. Summary
  160. Q&A
  161. Workshop
  162. Day 13. Creating Graphics and Multimedia: SVG and SMIL
  163. Introducing SVG
  164. Creating an SVG Document
  165. Creating Rectangles
  166. Adobe's SVG Viewer
  167. Using CSS Styles
  168. Creating Circles
  169. Creating Ellipses
  170. Creating Lines
  171. Creating Polylines
  172. Creating Polygons
  173. Creating Text
  174. Creating Gradients
  175. Creating Paths
  176. Creating Text Paths
  177. Creating Groups and Transformations
  178. Creating Animation
  179. Creating Links
  180. Creating Scripts
  181. Embedding SVG in HTML
  182. Introducing SMIL
  183. Summary
  184. Q&A
  185. Workshop
  186. Day 14. Handling XLinks, XPointers, and XForms
  187. Introducing XLinks
  188. Beyond Simple XLinks
  189. Introducing XPointers
  190. Introducing XBase
  191. Introducing XForms
  192. Summary
  193. Workshop
  194. Part III. In Review
  195. Part IV: At a Glance
  196. Day 15. Using JavaScript and XML
  197. Introducing the W3C DOM
  198. Introducing the DOM Objects
  199. Working with the XML DOM in JavaScript
  200. Searching for Elements by Name
  201. Reading Attribute Values
  202. Getting All XML Data from a Document
  203. Validating XML Documents by Using DTDs
  204. Summary
  205. Q&A
  206. Workshop
  207. Day 16. Using Java and .NET: DOM
  208. Using Java to Read XML Data
  209. Finding Elements by Name
  210. Creating an XML Browser by Using Java
  211. Navigating Through XML Documents
  212. Writing XML by Using Java
  213. Summary
  214. Q&A
  215. Workshop
  216. Day 17. Using Java and .NET: SAX
  217. An Overview of SAX
  218. Using SAX
  219. Using SAX to Find Elements by Name
  220. Creating an XML Browser by Using Java and SAX
  221. Navigating Through XML Documents by Using SAX
  222. Writing XML by Using Java and SAX
  223. Summary
  224. Q&A
  225. Workshop
  226. Day 18. Working with SOAP and RDF
  227. Introducing SOAP
  228. A SOAP Example in .NET
  229. A SOAP Example in Java
  230. Introducing RDF
  231. Summary
  232. Q&A
  233. Workshop
  234. Part IV. In Review
  235. Part V: At a Glance
  236. Day 19. Handling XML Data Binding
  237. Introducing DSOs
  238. Binding HTML Elements to HTML Data
  239. Binding HTML Elements to XML Data
  240. Binding HTML Tables to XML Data
  241. Accessing Individual Data Fields
  242. Binding HTML Elements to XML Data by Using the XML DSO
  243. Binding HTML Tables to XML Data by Using the XML DSO
  244. Searching XML Data by Using a DSO and JavaScript
  245. Handling Hierarchical XML Data
  246. Summary
  247. Q&A
  248. Workshop
  249. Day 20. Working with XML and Databases
  250. XML, Databases, and ASP
  251. Storing Databases as XML
  252. Using XPath with a Database
  253. Introducing XQuery
  254. Summary
  255. Q&A
  256. Workshop
  257. Day 21. Handling XML in .NET
  258. Creating and Editing an XML Document in .NET
  259. From XML to Databases and Back
  260. Reading and Writing XML in .NET Code
  261. Using XML Controls to Display Formatted XML
  262. Creating XML Web Services
  263. Summary
  264. Q&A
  265. Workshop
  266. Part V. In Review
  267. Appendix A. Quiz Answers
  268. Quiz Answers for Day 1
  269. Quiz Answers for Day 2
  270. Quiz Answers for Day 3
  271. Quiz Answers for Day 4
  272. Quiz Answers for Day 5
  273. Quiz Answers for Day 6
  274. Quiz Answers for Day 7
  275. Quiz Answers for Day 8
  276. Quiz Answers for Day 9
  277. Quiz Answers for Day 10
  278. Quiz Answers for Day 11
  279. Quiz Answers for Day 12
  280. Quiz Answers for Day 13
  281. Quiz Answers for Day 14
  282. Quiz Answers for Day 15
  283. Quiz Answers for Day 16
  284. Quiz Answers for Day 17
  285. Quiz Answers for Day 18
  286. Quiz Answers for Day 19
  287. Quiz Answers for Day 20
  288. Quiz Answers for Day 21
Recommended Book

Using SAX

Today's first example shows how to work with SAX. You'll start with the same example you used yesterday, except today, you'll use SAX. In particular, you're going to extract all the data from ch17_01.xml, which is shown in Listing 17.1.

Example 17.1. A Sample XML Document for Use with SAX Methods (ch17_01.xml)

<?xml version="1.0" encoding="UTF-8"?>
<session>
   <committee type="monetary">
       <title>Finance</title>
       <number>17</number>
       <subject>Donut Costs</subject>
       <date>7/15/2005</date>
       <attendees>
           <senator status="present">
               <firstName>Thomas</firstName>
               <lastName>Smith</lastName>
           </senator>
           <senator status="absent">
               <firstName>Frank</firstName>
               <lastName>McCoy</lastName>
           </senator>
           <senator status="present">
               <firstName>Jay</firstName>
               <lastName>Jones</lastName>
           </senator>
       </attendees>
   </committee>
</session>

How do you handle this XML document by using SAX? You start in the main method by calling a new version of the childLoop method created yesterday. This method will fill the same array of strings, displayText, and you'll store the number of strings in a variable named numberLines. When the childLoop method is done, all you have to do is display all the text in the displayText array:

import java.io.*;
import org.xml.sax.*;
import javax.xml.parsers.*;
import org.xml.sax.helpers.DefaultHandler;

public class ch17_02 extends DefaultHandler
{
    static int numberLines = 0;

       static String indentation = "";

       static String displayText[] = new String[1000];


       public static void main(String args[])

       {

           ch17_02 parser = new ch17_02();

           parser.childLoop(args[0]);


           for(int loopIndex = 0; loopIndex < numberLines; loopIndex++){

               System.out.println(displayText[loopIndex]);

           }
    }

In the childLoop method, start by creating a SAXParserFactory object, using a DefaultHandler object. The DefaultHandler object tells SAX which object to call when it encounters various nodes, and you'll use the present application object, which you've based on the DefaultHandler class:

public class ch17_02 extends DefaultHandler
{
        .
        .
        .

To refer to the current object, use the Java this keyword. Here's how to create the SAXParserFactory object:

public void childLoop(String uri)
{
    DefaultHandler saxHandler = this;

       SAXParserFactory saxFactory = SAXParserFactory.newInstance();
        .
        .
        .
}

Now create a new SAX parser by using this SAXParserFactory object, and this SAX parser will parse the XML document ch17_01.xml:

public void childLoop(String uri)
{
    DefaultHandler saxHandler = this;
    SAXParserFactory saxFactory = SAXParserFactory.newInstance();
    try {

           SAXParser saxParser = saxFactory.newSAXParser();

           saxParser.parse(new File(uri), saxHandler);

       } catch (Throwable t) {}
}

Table 17.1 lists the significant methods of the SAXParserFactory class, and Table 17.2 lists the significant methods of the SAXParser class.

Table 17.1. Methods of the javax.xml.parsers.SAXParserFactory Interface

Method

What It Does

protected SAXParserFactory()

Acts as the default constructor for the class.

boolean isNamespaceAware()

Returns True if the factory is configured to produce parsers that use XML namespaces.

boolean isValidating()

Returns True if the factory is configured to produce parsers that validate the XML content.

static SAXParserFactory newInstance()

Returns a new SAXParserFactory object.

abstract SAXParser newSAXParser()

Returns a new SAXParser object.

void setNamespaceAware(boolean awareness)

Requires that the created parser support XML namespaces.

void setValidating(boolean validating)

Requires that the parser produced validate XML documents.

Table 17.2. Methods of the SAXParser Class

Method

What It Does

protected SAXParser()

Acts as the default class constructor.

abstract Parser getParser()

Returns the SAX parser.

abstract boolean isNamespaceAware()

Returns True if this parser can understand namespaces.

abstract boolean isValidating()

Returns True if this parser is configured to validate XML documents.

void parse(File f, DefaultHandler dh)

Parses the file specified.

void parse(InputSource is, DefaultHandler dh)

Parses the content specified InputSource object.

void parse(InputStream is, DefaultHandler dh)

Parses the content of the specified InputStream object.

void parse(String uri, DefaultHandler dh)

Parses the content at the given URI, using the specified DefaultHandler object.

abstract void setProperty(String name, Object value)

Sets a property in the parser.

Now you've connected our SAX parser to our program and launched it, which means it will be calling various methods in your code to handle various types of nodes. It does this because you've based the program's main class on the SAX DefaultHandler class:

import java.io.*;
import org.xml.sax.*;
import javax.xml.parsers.*;
import org.xml.sax.helpers.DefaultHandler;

public class ch17_02 extends DefaultHandler
        .
        .
        .

The DefaultHandler class has a number of predefined methods, called callback methods, that the SAX parser will call:

  • characters — Called by the SAX parser for text nodes.
  • endDocument — Called by the SAX parser when the end of the document is seen.
  • endElement — Called by the SAX parser when the closing tag of an element is seen.
  • startDocument — Called by the SAX parser when the start of the document is seen.
  • startElement — Called by the SAX parser when the opening tag of an element is seen.

All the required callback methods are already implemented in the DefaultHandler class, but they don't do anything. That means we only have to implement the methods we want to use, such as startDocument to catch the beginning of the document or endDocument to catch the end of the document, as described later today. Table 7.3 lists the significant methods of the DefaultHandler class.

Table 17.3. Methods of the DefaultHandler Class

Method

What It Does

DefaultHandler()

Acts as the default class constructor.

void characters(char[] ch, int start, int length)

Handles text nodes.

void endDocument()

Handles the end of the document.

void endElement(String uri, String localName, String qName)

Handles the end of an element.

void error(SAXParseException e)

Handles a recoverable parser error.

void fatalError(SAXParseException e)

Reports a fatal parsing error.

void ignorableWhitespace(char[] ch, int start, int length)

Handles ignorable whitespace (such as that used to indent a document) in element content.

void notationDecl(String name, String publicId, String systemId)

Handles a notation declaration.

void processingInstruction(String target, String data)

Handles an XML processing instruction (such as a JSP directive).

InputSource resolveEntity(String publicId, String systemId)

Resolves an external entity.

void setDocumentLocator(Locator locator)

Sets a Locator object for document events.

void skippedEntity(String name)

Handles a skipped XML entity.

void startDocument()

Handles the beginning of the document.

void startElement(String uri, String localName, String qName, Attributes attributes)

Handles the start of an element.

void startPrefixMapping(String prefix, String uri)

Handles the start of a namespace mapping.

void unparsedEntityDecl(String name, String publicId, String systemId, String notationName)

Handles an unparsed entity declaration.

void warning(SAXParseException e)

Handles a parser warning.

Let's start by handling the start of the document.

Handling the Start of a Document

To handle the start of a document, you can implement the DefaultHandler startDocument method:

public void startDocument()
{
        .
        .
        .
}

When this method is called, the SAX processor has already seen the beginning of the document, so just put a generic XML declaration into the displayText array:

public void startDocument()
{
    displayText[numberLines] = indentation;

       displayText[numberLines] += "<?xml version=\"1.0\" encoding=\""+

           "UTF-8" + "\"?>";

       numberLines++;
}

Handling Processing Instructions

We can handle processing instructions by using the DefaultHandler processingInstruction method, which is called automatically when the SAX parser finds a processing instruction. The target of the processing instruction is passed to us, as is the data for the processing instruction, which means you can handle processing instructions like this:

public void processingInstruction(String target, String data)
{
    displayText[numberLines] = indentation;
    displayText[numberLines] += "<?";
    displayText[numberLines] += target;
    if (data != null && data.length() > 0) {
        displayText[numberLines] += ' ';
        displayText[numberLines] += data;
    }
    displayText[numberLines] += "?>";
    numberLines++;
}

Handling the Start of an Element

To handle the start of an element, use the startElement SAX method. This method is passed the namespace URI of the element, the local (unqualified) name of the element, the qualified name of the element, and the element's attributes (as an Attributes object):

public void startElement(String uri, String localName, String qualifiedName,
    Attributes attributes)
{
        .
        .
        .
}

Store the element's name in our displayText array, like this:

public void startElement(String uri, String localName, String qualifiedName,
    Attributes attributes)
{
    displayText[numberLines] = indentation;


       indentation += "    ";


       displayText[numberLines] += '<';

       displayText[numberLines] += qualifiedName;

           .

           .

           .

       displayText[numberLines] += '>';

       numberLines++;
}

So far, so good. But what if the element has attributes?

Handling Attributes

If the element has attributes, loop over them. And the way you determine whether the element has attributes is by checking whether the Attributes object passed to you in the startElement method is null:

public void startElement(String uri, String localName, String qualifiedName,
    Attributes attributes)
{
    displayText[numberLines] = indentation;

    indentation += "    ";

    displayText[numberLines] += '<';
    displayText[numberLines] += qualifiedName;
    if (attributes != null) {

           .

           .

           .

       }
    displayText[numberLines] += '>';
    numberLines++;
}

Table 17.4 lists the methods of Attributes objects. We can reach the attributes in an object that implements this interface based on index, name, or namespace-qualified name.

Table 17.4. Attributes Interface Methods

Method

What It Does

int getIndex(java.lang.String uri, java.lang.String localPart)

Returns the index of an attribute, by namespace and local name.

int getIndex(java.lang.String qualifiedName)

Returns the index of an attribute, given its qualified name.

int getLength()

Returns the number of attributes in the list.

java.lang.String getLocalName(int index)

Returns an attribute's local name, by index.

java.lang.String getQName(int index)

Returns an attribute's qualified name, by index.

java.lang.String getType(int index)

Returns an attribute's type, by index.

java.lang.String getType-(java.lang.String qualifiedName)

Returns an attribute's type, by qualified name.

java.lang.String getType(java.lang.String uri, java.lang.String localName)

Returns an attribute's type, by namespace and local name.

java.lang.String getURI(int index)

Returns an attribute's namespace URI, by index.

java.lang.String getValue(int index)

Returns an attribute's value, by index.

java.lang.String getValue-(java.lang.String qualifiedName)

Returns an attribute's value, by qualified name.

java.lang.String getValue(java.lang.String uri, java.lang.String localName)

Returns an attribute's value, by namespace name and local name.

Now loop over the attributes and use the getQName (get qualified name) and getValue methods to store the name and value of each attribute:

public void startElement(String uri, String localName, String qualifiedName,
    Attributes attributes)
{
    displayText[numberLines] = indentation;

    indentation += "    ";

    displayText[numberLines] += '<';
    displayText[numberLines] += qualifiedName;
    if (attributes != null) {
        int numberAttributes = attributes.getLength();

           for (int loopIndex = 0; loopIndex < numberAttributes; loopIndex++) {

               displayText[numberLines] += ' ';

               displayText[numberLines] += attributes.getQName(loopIndex);

               displayText[numberLines] += "=\"";

               displayText[numberLines] += attributes.getValue(loopIndex);

               displayText[numberLines] += '"';

           }
    }
    displayText[numberLines] += '>';
    numberLines++;
}

Next, you'll take a look at handling text.

Handling Text

In SAX, you handle text by using the characters method. This method is passed an array of characters, the location in that array where the text for the current text node starts, and the length of the text in the text node:

public void characters(char characters[], int start, int length)
{
    .
    .
    .
}

Here's how to handle the text of a text node, adding it to the displayText array:

public void characters(char characters[], int start, int length)
{
    String characterData = (new String(characters, start, length)).trim();

       if(characterData.indexOf("\n") < 0 && characterData.length() > 0) {

           displayText[numberLines] = indentation;

           displayText[numberLines] += characterData;

           numberLines++;

       }
}

By default, the SAX parser will also call a method named ignorableWhitespace when it finds whitespace text nodes, such as whitespace used for indentation. If we want to handle that text like any other text, we can simply pass it on to the characters method we just implemented (note that we've commented this line out here because we're supplying our own indentation in this example):

public void ignorableWhitespace(char characters[], int start, int length)
{
    //characters(characters, start, length);
}

Handling the End of Elements

Besides the startElement method, which is called when the SAX parser sees the beginning of an element, we can also implement the endElement method to handle an element's closing tag. Here's how that looks in this example:

public void endElement(String uri, String localName, String qualifiedName)
{
    indentation = indentation.substring(0, indentation.length() - 4);
    displayText[numberLines] = indentation;
    displayText[numberLines] += "</";
    displayText[numberLines] += qualifiedName;
    displayText[numberLines] += '>';
    numberLines++;
}

Handling Errors and Warnings

SAX makes it easy to handle warnings and errors. We can implement the warning method to handle warnings, the error method to handle errors, and the fatalError method to handle errors that the SAX parser considers fatal enough to make it stop processing. Here's what the error handling looks like in this example:

public void warning(SAXParseException exception)
{
    System.err.println("Warning: " +
        exception.getMessage());
}

public void error(SAXParseException exception)
{
    System.err.println("Error: " +
        exception.getMessage());
}

public void fatalError(SAXParseException exception)
{
    System.err.println("Fatal error: " +
        exception.getMessage());
}

And that's it—now run your new SAX code and parse ch17_01.xml like this:

%java ch17_02 ch17_01.xml

As shown in Figure 17.1, we've been able to read and extract all the data in the XML document by using SAX methods.

17fig01.gif

Figure 17.1 Parsing an XML document by using a SAX parser.

The complete Java code is in Listing 17.2.

Example 17.2. Parsing an XML Document by Using Java SAX (ch17_02.java)

import java.io.*;
import org.xml.sax.*;
import javax.xml.parsers.*;
import org.xml.sax.helpers.DefaultHandler;

public class ch17_02 extends DefaultHandler
{
    static int numberLines = 0;
    static String indentation = "";
    static String displayText[] = new String[1000];

    public static void main(String args[])
    {
        ch17_02 parser = new ch17_02();
        parser.childLoop(args[0]);

        for(int loopIndex = 0; loopIndex < numberLines; loopIndex++){
            System.out.println(displayText[loopIndex]);
        }
    }

    public void childLoop(String uri)
    {
        DefaultHandler saxHandler = this;
        SAXParserFactory saxFactory = SAXParserFactory.newInstance();
        try {
            SAXParser saxParser = saxFactory.newSAXParser();
            saxParser.parse(new File(uri), saxHandler);
        } catch (Throwable t) {}
    }

    public void startDocument()
    {
        displayText[numberLines] = indentation;
        displayText[numberLines] += "<?xml version=\"1.0\" encoding=\""+
            "UTF-8" + "\"?>";
        numberLines++;
    }

    public void processingInstruction(String target, String data)
    {
        displayText[numberLines] = indentation;
        displayText[numberLines] += "<?";
        displayText[numberLines] += target;
        if (data != null && data.length() > 0) {
            displayText[numberLines] += ' ';
            displayText[numberLines] += data;
        }
        displayText[numberLines] += "?>";
        numberLines++;
    }

    public void startElement(String uri, String localName,
        String qualifiedName, Attributes attributes)
    {
        displayText[numberLines] = indentation;

        indentation += "    ";

        displayText[numberLines] += '<';
        displayText[numberLines] += qualifiedName;
        if (attributes != null) {
            int numberAttributes = attributes.getLength();
            for (int loopIndex = 0; loopIndex < numberAttributes; loopIndex++){
                displayText[numberLines] += ' ';
                displayText[numberLines] += attributes.getQName(loopIndex);
                displayText[numberLines] += "=\"";
                displayText[numberLines] += attributes.getValue(loopIndex);
                displayText[numberLines] += '"';
            }
        }
        displayText[numberLines] += '>';
        numberLines++;
    }

    public void characters(char characters[], int start, int length)
    {
        String characterData = (new String(characters, start, length)).trim();
        if(characterData.indexOf("\n") < 0 && characterData.length() > 0) {
            displayText[numberLines] = indentation;
            displayText[numberLines] += characterData;
            numberLines++;
        }
    }

    public void ignorableWhitespace(char characters[], int start, int length)
    {
        //characters(characters, start, length);
    }

    public void endElement(String uri, String localName, String qualifiedName)
    {
        indentation = indentation.substring(0, indentation.length() - 4);
        displayText[numberLines] = indentation;
        displayText[numberLines] += "</";
        displayText[numberLines] += qualifiedName;
        displayText[numberLines] += '>';
        numberLines++;
    }

    public void warning(SAXParseException exception)
    {
        System.err.println("Warning: " +
            exception.getMessage());
    }

    public void error(SAXParseException exception)
    {
        System.err.println("Error: " +
            exception.getMessage());
    }

    public void fatalError(SAXParseException exception)
    {
        System.err.println("Fatal error: " +
            exception.getMessage());
    }
}

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.