This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: The duplicate class registration problem]
- To: java at gcc dot gnu dot org
- Subject: Re: The duplicate class registration problem]
- From: Torsten Rüger <torsten dot rueger at firsthop dot com>
- Date: Fri, 26 Oct 2001 11:28:07 +0300
- References: <1003994234.3798.ezmlm@gcc.gnu.org> <3BD8770C.9A19C99A@pacbell.net> <002801c15d98$204fd700$5be6b4cd@cygnus.com>
Anthony Green wrote:
>>SAX has always provided bootstrapping APIs, but DOM has yet to standardize
>>on them
No. Just it isn't maybe widely known yet. Read
http://java.sun.com/xml/jaxp/dist/1.1/docs/api/ .
You can write :
javax.xml.parsers.DocumentBuilderFactory.
newInstance().
newDocumentBuilder().parse(File/InputStream)
and get back an or.w3c.dom.Document without ever having touched a
specific implementation. (Yes this works in Xerces 1.4.*)
But then you can also read the header of the javax. imlementation that
Xerces comes with :
ATTENTION: THIS IMPLEMENTATION OF THE "JAVAX.XML.PARSER" CLASSES IS NOT
THE OFFICIAL REFERENCE IMPLEMENTATION OF THE JAVA SPECIFICATION REQUEST
5 FOUND AT
http://java.sun.com/aboutJava/communityprocess/jsr/jsr_005_xml.html
THIS IMPLEMENTATION IS CONFORMANT TO THE "JAVA API FOR XML PARSING"
SPECIFICATION VERSION 1.1 PUBLIC REVIEW 1 BY JAMES DUNCAN DAVIDSON
PUBLISHED BY SUN MICROSYSTEMS ON NOV. 2, 2000 AND FOUND AT
http://java.sun.com/xml
And there we are again, back to our problem of duplicate classes. With
the "standards" being so much in the flux, I suggest it's best you leave
the user to choose which "standard" he wants/needs to use.
Cheers
Torsten