Lists Home |
Date Index |
- From: David Megginson <email@example.com>
- To: firstname.lastname@example.org
- Date: Mon, 13 Apr 1998 16:15:00 -0400
Dmitri Kondratiev writes:
> >This is a very good question. Originally, there was a
> >com.microstar.sax.AElfredDriver that was distributed together with
> >LarkDriver, MSXMLDriver, and NXPDriver. Eventually, I would like to
> >see all of the com.microstar.sax.* drivers disappear, as these parsers
> >include native SAX drivers in their own packages. I removed
> >com.microstar.sax.AElfredDriver when I included a native SAX driver in
> >the AElfred 1.1 distribution.
> This means that support for SAX in AElfred becomes a _special case_ that
> application will have to recognize !
Just the opposite. Most Java-based XML parsers now have native SAX
drivers in their own packages:
IBM XML for Java: com.ibm.xml.parser.SAXDriver
The two drivers in com.microstar.sax are the special cases, and they
will disappear once MSXML and Lark have native SAX drivers.
As for your other question, about determining what drivers are
available, there are a few options: I am going to recommend that we
use the property "sax.parser" to provide the class name for the
default SAX driver in Java implementations (I don't know the politics
of property names, though).
All the best,
David Megginson email@example.com
Microstar Software Ltd. firstname.lastname@example.org
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)