Home arrow XML arrow Java and XML Basics, Part 3

Java and XML Basics, Part 3

So far, during this series of articles (part 1, part 2) we've looked at DOM and SAX, and I suppose most of you are thinking which one of the two approaches is preferable? Well, there is no general rule of thumb, but this article might help you make the right decision when you’ll have to.

Author Info:
By: Liviu Tudor
Rating: 5 stars5 stars5 stars5 stars5 stars / 25
April 20, 2004
  1. · Java and XML Basics, Part 3
  2. · Which One is the Better One to Use?
  3. · Running the Parser
  4. · Problems with Big XML Files
  5. · Validating Parsers - DOM
  6. · Where do We Get a Validating Parser?
  7. · ErrorHandler
  8. · Validating Parsers - SAX
  9. · Conclusion

print this article

Java and XML Basics, Part 3
(Page 1 of 9 )

NOTE  Before you get started, you'll probably want to download the support file (70KB) which contains sample codes for all articles in this series up to this point.)

Performance Considerations

Those of you who read the previous article and manage not to fall asleep before the end will probably remember our little (silly) XML example that was parsed using both the DOM and the SAX approach. As we have seen, both of them achieved the same thing, which raises the obvious questions:

  • Why have 2 ways of doing the same thing?
  • Which one is the better one to use?

Oh yeah, there is always the 3rd question about the meaning of life --but we will leave that one for the time being. (It's more of a Linux programming question, anyway.)

The reason for having these two ways of doing things is due to the fact that the two standards come from different sources: as we stated before, DOM was produced by W3C while SAX came from David Megginson. Also, the two standards are based on two different paradigms -- while DOM produces a document tree at the end of the parsing process, which can then be manipulated/interrogated, by the user, SAX is based on the idea of events and leaves the whole data manipulation (and eventually building a document tree) to the user. (Not to mention of course that having just one way to do this would be rather boring -- a bit like having only one type of coffee and not being able to enjoy such delicacies as Cappuccino, or a Mocha Latte.)

blog comments powered by Disqus

- Open XML Finally Supported by MS Office
- XML Features Added to Two Systems
- Using Regions with XSL Formatting Objects
- Using XSL Formatting Objects
- More Schematron Features
- Schematron Patterns and Validation
- Using Schematron
- Datatypes and More in RELAX NG
- Providing Options in RELAX NG
- An Introduction to RELAX NG
- Path, Predicates, and XQuery
- Using Predicates with XQuery
- Navigating Input Documents Using Paths
- XML Basics
- Introduction to XPath

Watch our Tech Videos 
Dev Articles Forums 
 RSS  Articles
 RSS  Forums
 RSS  All Feeds
Write For Us 
Weekly Newsletter
Developer Updates  
Free Website Content 
Contact Us 
Site Map 
Privacy Policy 

Developer Shed Affiliates


© 2003-2019 by Developer Shed. All rights reserved. DS Cluster - Follow our Sitemap
Popular Web Development Topics
All Web Development Tutorials