[Xerces-J] architecture question

[Gregory Krasnow <ga...@STONEANALYTICS.com>]

Since it seems like many of the classes one needs to use regardless of
parser come form org.xml.sax, am I correct in assuming that Xerces is
basically a SAX parser that has implemented a DOM tree from the SAX parser??
 
- Greg
 
Gregory Krasnow
Senior Software Engineer
Stone Analytics, Inc.
gak@stics.com <ma...@stics.com> 
Tel: 619.503.7540 x204
Fax: 619.503-7541
www.stonenalytics.com <http://www.stonenalytics.com/> 
 

Re: [Xerces-J] architecture question

[Andy Clark <an...@apache.org>]

Gregory Krasnow wrote:
> Since it seems like many of the classes one needs to use regardless 
> of parser come form org.xml.sax, am I correct in assuming that 
> Xerces is basically a SAX parser that has implemented a DOM tree 
> from the SAX parser??

If you look at the code, you'll notice that we created an internal
kind of "super SAX" which passes through all of the relevant info
as it's encountered in the document. From these internal callbacks
we call the SAX handlers (in the SAX parser) and build a DOM
Document (in the DOM parser). But the parser is not strictly a
SAX parser as defined by the handler interfaces defined in SAX.

-- 
Andy Clark * IBM, JTC - Silicon Valley * andyc@apache.org