On November 9, 1999, the Apache Software Foundation announced
the creation of the xml.apache.org project for Open
Source XML solutions. As part of that announcment, IBM announced that
it was donating its XML4J, XML4C and LotusXSL technologies to the
xml.apache.org project. The
parsing technologies have been renamed Xerces, and the LotusXSL
technology has been renamed Xalan. IBM is shifting its XML parsing
development resources to work on the Xerces parsers, with the intent
of using the Xerces code base as the foundation for XML4J and XML4C.
This version of XML4J is based on the Apache Xerces codebase.
What's the difference betweeen XML4J and Xerces
This version of XML4J has been tested internally at IBM, beyond
the testing that is done by the xml.apache.org project. In
addition, we are providing a compatibility jar for customers
migrating from the XML4J 2.0.x native API. The TX compatability
API's are no longer present in the XML4J 3.0.x series.
Please note that the names of the main .jar files have changed
from xml4j.jar to Xerces.jar and from xml4jSamples.jar to XercesSamples.jar
How do I use the com.ibm. compatibility classes?
In order to use the 2.0.x compatibility classes, you need to
include the xml4j.jar jar file in your CLASSPATH, in addition to the
Xerces.jar. There are four classes in the jar:
com.ibm.xml.parsers.SAXParser
com.ibm.xml.parsers.ValidatingSAXParser
com.ibm.xml.parsers.NonValidatingDOMParser
com.ibm.xml.parsers.DOMParser
The future direction for the parser instantiation classes is the
parser instantiation API that wil result from the W3C's DOM Level 3
effort, which is just getting underway.
Is IBM making any additional support guarantees with XML4J?
IBM is not making any additional support guarantees for XML4J.
In particular, IBM is not certifying that XML4J is Y2K compliant.
XML4J makes no internal date calculations.
Change history
December 9, 1999: version 3.0.0EA3
First version derived from Xerces-J code base.
Supply XML4J 2.0.x compatibility API.