[jdom-interest] Feature Request

[Chris B.]

Elliotte Rusty Harold wrote:

> The problem here is a design flaw in Xerces. It assumes you will only 
> ever want one parser configuration in the same VM. (This is not an 
> XMLReader. This is an internal, non-standard class in Xerces.) Thus 
> once the parser configuration has been set through the appropriate 
> system property or default, you're stuck with it for all your Xerces 
> parsing. Possibly you could change the system property in your code, 
> but I'm not sure whether that would work or not.


Correct me if I'm wrong, but wouldn't it have been better if NekoHTML 
wasn't written to conform to the non-standard Xerces class, but rather 
if it implemented an XMLReader?

As I understand it, this is the role of XMLReader - to generate an XML 
stream from some source.