Non validating sax parser
While that suite has only been published relatively recently, many of its key components have been well known to the XML community for over a year and a half; they shouldn't come as a big surprise for any implementor.Many of these tests have been used for basic quality testing in a variety of XML processors.By comparison, with a SAX parser you have to know exactly what you're looking for at the time you parse.Useful if you're unmarshalling JAXB objects or extracting data from a large file, not so useful if you're exploring a data structure.We will provide you with the hard data from our tests, so you can independently evaluate every claim made in this article and reproduce the results yourself.The results leverage the freely available OASIS XML Conformance Test Suite.One indication of XML's success is that a dozen or so implementations of an XML processor exist.These processors, spanning a variety of programming environments, are at the core of a new generation of web tools that are revolutionizing the dynamic generation of HTML and enabling new types of web applications, including business-to-business data messaging.
The parser implements SAX2 and JAXP 1.1 parser interfaces.It has no DOM support, and no support for validation: in fact, it is about as stripped-down as an XML parser can get. The SAX2 and JAXP libraries are not included in the package; these must be installed separately.They are available automatically if you use JDK 1.4. The JAR file includes no manifest, so placing the JAR file on your classpath will not make this the default JAXP parser.Nevertheless, the Ælfred parser offered some advantages over the Crimson parser included with JDK 1.4, and it is therefore now available as a free-standing download.This version branched some while ago from the version developed by David Brownell (see here), which is now packaged in the GNU XML library.