SAX and delayed entity loading

[david at megginson.com]

Gabe Beged-Dov writes:

 > What should a non-validating SAX parser do with the external entity if it
 > isn't going to try to resolve it? The XML spec (sec.4.4.3) says the
 > processormust inform the application that the entity has been encountered.

This has been pointed out as either a design flaw or feature in SAX,
depending on whether you consider the EntityResolver to be part of the 
application or part of the parser.  SAX forces the choice about
resolving external entities to be made by the SAX client, not by the
SAX driver (the client can choose to ignore an external entity by
returning an empty character stream).


All the best,


David

-- 
David Megginson                 david at megginson.com
           http://www.megginson.com/

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)