This is the mail archive of the java@gcc.gnu.org mailing list for the Java project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: The duplicate class registration problem]


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]