World-renowned, best-selling author Elliotte Rusty Harold teaches Java programmers how to put XML to work!
° Author is uniquely qualified to write this book! He is the author of numerous wellreceived books on Java and has written two of the best-selling books on XML. This is the book that brings his skills together.
° Harold has a fantastic reputation, is skilled, and has excellent publicity channels.
° A complete tutorial about writing Java programs that read and write XML documents.
Java is the ideal language for processing XML documents. Consequently, more XML tools have been written in Java than in any other language. More open source XML tools are written in Java than in any other language. Processing XML with Java fills an immediate need for developers who are working with XML in Java. It is a comprehensive tutorial and reference to the major APIs. This book shows developers how to: save XML documents from their applications written in Java; read XML documents produced by other programs; communicate with network servers that send and receive XML data; validate documents they receive against DTDs, schemas, and business rules; and integrate XSLT into their programs.
Click below for Web Resources related to this title:
Author's Web Site
Click below for Sample Chapter(s) related to this title:
(NOTE: Each chapter concludes with a Summary.)
List of Examples.
List of Figures.
Who You Are.
What You Need to Know.
What You Need to Have.
How to Use This Book.
The Online Edition.
Some Grammatical Notes.
Contacting the Author.
I. XML.1. XML for Data.
A Thought Experiment.
Elements and Tags.
The Last Mile.
Associating Stylesheets with XML Documents.
XSL.2. XML Protocols: XML-RPC and SOAP.
XML as a Message Format.
HTTP as a Transport Protocol.
How HTTP Works.
HTTP in Java.
Customizing the Request.
How HTTP POST Works.
A SOAP Example.
Posting SOAP Documents.
Custom Protocols.3. Writing XML with Java.
Better Coding Practices.
Producing Valid XML.
Output Streams, Writers, and Encodings.
A Simple XML-RPC Client.
A Simple SOAP Client.
Servlets.4. Converting Flat Files to XML.
Determining the Output Format.
Building Hierarchical Structures from Flat Data.
Alternatives to Java.
Imposing Hierarchy with XSLT.
The XML Query Language.
Relational Databases.5. Reading XML.
InputStreams and Readers.
Choosing an XML API.
Choosing an XML Parser.
II. SAX.6. SAX.
What Is SAX?
Using the ContentHandler.
The DefaultHandler Adapter Class.
Receiving Processing Instructions.
Receiving Namespace Mappings.
“Ignorable White Space”.
Receiving Skipped Entities.
What the ContentHandler Doesn't Tell You.7. The XMLReader Interface.
Building Parser Objects.
Exceptions and Errors.
The ErrorHandler Interface.
Features and Properties.
Getting and Setting Features.
Getting and Setting Properties.
Xerces Custom Features.
Xerces Custom Properties.
DTDHandler.8. SAX Filters.
The Filter Architecture.
The XMLFilter Interface.
Filters That Add Content.
Filters versus Transforms.
The XMLFilterImpl Class.
Parsing Non-XML Documents.
The Document Object Model.
The Evolution of DOM.
What Is and Isn't in the Tree.
DOM Parsers for Java.
Parsing Documents with a DOM Parser.
JAXP DocumentBuilder and DocumentBuilderFactory.
DOM3 Load and Save.
The Node Interface.
Navigating the Tree.
Modifying the Tree.
The NodeList Interface.
Choosing between SAX and DOM.10. Creating XML Documents with DOM.
Locating a DOMImplementation.
The Document Interface as an Abstract Factory.
The Document Interface as a Node Type.
Transferring Nodes between Documents.
Normalization.11 The DOM Core.
The Element Interface.
The NamedNodeMap Interface.
The CharacterData Interface.
The Text Interface.
The CDATASection Interface.
The EntityReference Interface.
The Attr Interface.
The ProcessingInstruction Interface.
The Comment Interface.
The DocumentType Interface.
The Entity Interface.
The Notation Interface.12. The DOM Traversal Module.
Constructing NodeIterators with DocumentTraversal.
Filtering by Node Type.
TreeWalker.13. Output from DOM.
DOM Level 3.
IV. JDOM.14. JDOM.
What Is JDOM?
Creating XML Elements with JDOM.
Creating XML Documents with JDOM.
Writing XML Documents with JDOM.
Document Type Declarations.
Reading XML Documents with JDOM.
Navigating JDOM Trees.
Talking to DOM Programs.
Talking to SAX Programs.
Serializing JDOM Objects.
Synchronizing JDOM Objects.
What JDOM Doesn't Do.15. The JDOM Model.
The Document Class.
The Element Class.
Navigation and Search.
The Attribute Class.
The Text Class.
The CDATA Class.
The ProcessingInstruction Class.
The Comment Class.
The DocType Class.
The EntityRef Class.
V. XPath/XSLT.16. XPath.
The XPath Data Model.
Compound Location Paths.
Absolute Location Paths.
Abbreviated Location Paths.
Combining Location Paths.
XPath with Saxon.
XPath with Xalan.
DOM Level 3 XPath.
Taking the Value of a Node.
The Default Template Rules.
Calling Templates by Name.
The xml-stylesheet Processing Instruction.
XSLT Processor Attributes.
Passing Parameters to Stylesheets.
Sources and Results.
Extending XSLT with Java.
VI. APPENDIXES.Appendix A: XML API Quick Reference.
The DOM Data Model.
org.xmlpull.v1.Appendix B: SOAP 1.1 Schemas.
The SOAP 1.1 Envelope Schema.
The SOAP 1.1 Encoding Schema.
W3C Software Notice and License.Appendix C: Recommended Reading.
One night five developers, all of whom wore very thick glasses and had recently been hired byElephants, Inc., the world's largest purveyor of elephants and elephant supplies, were familiarizingthemselves with the company's order processing system when they stumbled into a directoryfull of XML documents on the main server. "What's this?" the team leader asked excitedly.None of them had ever heard of XML before so they decided to split up the files between themand try to figure out just what this strange and wondrous new technology actually was.
The first developer, who specialized in optimizing Oracle databases, printed out a stack of FMPXMLRESULTdocuments generated by the FileMaker database where all the orders werestored, and began pouring over them. "So this is XML! Why, it's nothing novel. As anyone cansee who's able, an XML document is nothing but a table!"
"What do you mean, a table?" replied the second programmer, well versed in object orientedtheory and occupied with a collection of XMI documents that encoded UML diagrams for thesystem. "Even a Visual Basic programmer could see that XML documents aren't tables. Duplicatesaren't allowed in a table relation, unless this is truly some strange mutation. Classes andobjects is what these document are. Indeed, it should be obvious on the very first pass. An XMLdocument is an object and a DTD is a class."
"Objects? A strange kind of object, indeed!" said the third developer, a web designer of somerenown, who had loaded the XHTML user documentation for the order processing system intoMozilla. "I don't see any types at all. If you think this is an object, then it's your software Irefuse to install. But with all those stylesheets there, it should be clear to anyone not sedated,that XML is just HTML updated!"
"HTML? You must be joking" said the fourth, a computer science professor on sabbatical fromMIT, who was engrossed in an XSLT stylesheet that validated all the other documents against aSchematron schema. "Look at the clean nesting of hierarchical structures, each tag matching itspartner as it should. I've never seen HTML that looks this good. What we have here is Sexpressions,which is certainly nothing new. Babbage invented this back in 1882!"
"S expressions?" queried the technical writer, who was occupied with documentation for theproject written in DocBook. "Maybe that means something to those in your learned profession.But to me, this looks just like a FrameMaker MIF file. However, locating the GUI does seem tobe taking me awhile."
And so they argued into the night, none of them willing to give an inch, all of them presentingstill more examples to prove their points, none of them bothering to look at the others' examples.Indeed, they're probably still arguing today. You can even hear their shouts from time totime on xml-dev. Their mistake, of course, was in trying to force XML into the patterns of technologiesthey were already familiar with rather than taking it on its own terms. XML can storedata, but it is not a database. XML can serialize objects, but an XML document is not an object.Web pages can be written in XML, but XML is not HTML. Functional (and other) programminglanguages can be written in XML, but XML is not a programming language. Books arewritten in XML, but that doesn't make XML desktop publishing software.
XML is something truly new that has not been seen before in the world of computing. Therehave been precursors to it, and there are always fanatics who insist on seeing XML throughdatabase (or object, or functional, or S-expression) colored glasses. But XML is none of thesethings. It is something genuinely unique and new in the world of computing; and it can only beunderstood when you're willing to accept it on its own terms, rather than forcing it into yesterday'spigeon holes.
There are a lot of tools, APIs, and applications in the world that try to pretend XML is somethingmore familiar to programmers; that it's just a funny kind of database, or just like an object,or just like remote procedure calls. These APIs are occasionally useful in very restricted andpredictable environments. However, they are not suitable for processing XML in its most generalformat. They work well in their limited domains, but they fail when presented with XMLthat steps outside the artificial boundaries they've defined. XML was designed to be extensible,but it's a sad fact that many of the tools designed for XML aren't nearly as extensible as XMLitself.
This book is going to show you how to handle XML in its full generality. It pulls no punches. Itdoes not pretend that XML is anything except XML, and it shows you how to design your programsso that they handle real XML in all its messiness: valid and invalid, mixed and unmixed,typed and untyped, and both all and none of these at the same time. To that end, this book focuseson those APIs that don't try to hide the XML. In particular, there are three major JavaAPIs that correctly model XML, as opposed to modeling a particular class of XML documentsor some narrow subset of XML. These are:
These APIs are the core of this book. In addition I cover a number of preliminaries and supplementsto the basic APIs including:
And, since we're going to need a few examples of XML applications to demonstrate the APIswith, I also cover XML-RPC, SOAP, and RSS in some detail. However, the techniques thisbook teaches are hardly limited to just those three applications.
This book is written for experienced Java programmers who want to integrate XML into theirsystems. Java is the ideal language for processing XML documents. Its strong Unicode supportin particular made it the preferred language for many early implementers. Consequently, moreXML tools have been written in Java than in any other language. More open source XML toolsare written in Java than in any other language. More programmers process XML in Java than inany other language.Processing XML with Java will teach you how to:
This book is meant for Java programmers who need to do anything with XML. It teaches thefundamentals and advanced topics, leaving nothing out. It is a comprehensive course in processingXML with Java that takes developers from little knowledge of XML to designing sophisticatedXML applications and parsing complicated documents. The examples cover a wide rangeof possible uses including file formats, data exchange, document transformation, database integration,and more.
This is not an introductory book with respect to either Java or XML. I assume you have substantialprior experience with Java and preferably some experience with XML. On the Java side, Iwill freely use advanced features of the language and its class library without explanation orapology. Among other things, I assume you are thoroughly familiar with:
In addition, in one or two places in this book I'm going to use some SQL and JDBC. However,these sections are relatively independent of the rest of the book; and chances are if you aren't alreadyfamiliar with SQL, then you don't need the material in these sections anyway.
XML is deliberately architecture, platform, operating system, GUI, and language agnostic (infact, more so than Java). It works equally well on Mac OS, Windows, Linux, OS/2, various flavorsof Unix, and more. It can be processed with Python, C++, Haskell, ECMAScript, C#, Perl,Visual Basic, Ruby, and of course Java. No byte order issues need concern you if you switch betweenPowerPC, X86, or other architectures. Almost everything in this book should workequally well on any platform that's capable of running Java.
Most of the material in this book is relatively independent of the specific Java version. Java 1.4bundles SAX, DOM, and a few other useful classes into the core JDK. However, these are easilyinstalled in earlier JVMs as open source libraries from the Apache XML Project and othervendors. For the most part, I used Java 1.3 and 1.4 when testing the examples; and it's possiblethat a few classes and methods have been used that are not available in earlier versions. In mostcases, it should be fairly obvious how to backport them. All of the basic XML APIs exceptTrAX should work in Java 1.1 and later. TrAX requires Java 1.2 or later.
This book is organized as an advanced tutorial that can also serve as a solid and comprehensivereference. The first chapter covers the bare minimum material needed to start working withXML, though for the most part this is intended more as a review for readers who've alreadyread other, more basic books than as a comprehensive introduction. The second chapter introducesRSS, XML-RPC, and SOAP, the XML applications we'll be using for examples in therest of the book. This is followed by two chapters on generating XML from your own programs(a subject which is all too often presented as a lot more complicated than it actually is). The firstcovers generating XML directly from code. The second covers converting legacy data in otherformats to XML. The remaining bulk of the book is devoted to the major APIs for processingXML:
Finally, the book finishes with an appendix providing quick references to the main APIs.If you have limited experience with XML, I suggest you read at least the first five chapters inorder. From that point forward, if you have a particular API preference, you may begin with thepart covering the major API you're interested in:
Once you're comfortable with one or more of these APIs, you can read Chapters 16 and 17 onXPath and XSLT. However, those APIs and chapters do require some knowledge of at least oneof the three major APIs.
Click below to download the Index file related to this title: