SAX 2.0 Changes
This page provides a detailed list of the changes between the different development versions of the SAX2 API. The largest changes were between SAX 1.0 and SAX 2.0beta. There was an alpha release that was substantially more like SAX 1.0, which is not described here.
Note that the changes after the SAX 2.0 release are not detailed here as much as the earlier changes, because complete CVS history (with a separate ChangeLog) is available.
Changes from SAX 2.0 r2pre3 to SAX 2.0.1
SAX 2.0.1 was released on 29 January 2002.
Changes from SAX 2.0 r2pre2 to SAX 2.0 r2pre3
SAX 2.0 r2pre3 was released on 20 November 2001.
Changes from SAX 2.0 r2pre1 to SAX 2.0 r2pre2
SAX 2.0 r2pre2 was released on 17 October 2001. Most of the fixes were publicly available through CVS at Sourceforge since early July, and resolved bugs filed against SAX at SourceForge.
Changes from SAX 2.0 to SAX 2.0 r2pre1
SAX 2.0 r2pre1 was released on 28 December 2000.
Changes from SAX 2.0prerelease to SAX 2.0
Changes from SAX 2.0beta2 to SAX 2.0prerelease
Changes from SAX 2.0beta to SAX 2.0beta2
Changes from SAX 1.0 to SAX 2.0beta
The following interfaces and classes have been deprecated, and will be removed from a future version of SAX; they should be used only for interaction with SAX1 drivers or applications:
The following interfaces and classes have been added to SAX2:
SAX2 contains complete Namespace support, which is available by default from any XMLReader. An XML reader can also optionally supply raw XML 1.0 names. See the Namespaces page for more details.
An XML reader is fully configurable: it is possible to attempt to query or change the current value of any feature or property. Features and properties are identified by fully-qualified URIs, and parties are free to invent their own names for new extensions. See the Features and Properties page for more details.
The ContentHandler and Attributes interfaces are similar to the deprecated DocumentHandler and AttributeList interfaces, but they add support for Namespace-related information. ContentHandler also adds a callback for skipped entities, and Attributes adds the ability to look up an attribute's index by name.
The ParserAdapter class makes a SAX1 Parser behave as a SAX2 XMLReader. The XMLReaderAdapter class makes a SAX2 XML reader behave as a SAX1 parser. These two classes should ease the transition from SAX1 to SAX2 by allowing SAX1 drivers and clients to co-exist with SAX2 drivers and clients in the same application.
SAX1 Bugs Fixed