[jdom-interest] Feature Request

Elliotte Rusty Harold elharo at metalab.unc.edu
Fri Feb 20 05:37:24 PST 2004

At 6:52 PM -0800 2/19/04, Jeremy.Prellwitz at siras.com wrote:
>It is not NekoHTML that i'm worried about.  It is parsing regular XML
>documents in the same webapp.  Basically, NekoHTML interferes with the
>creation of Xerces parsers'.    When i create a SAXBuilder object, it
>creates a parser that is using the HTML configuration setup by NekoHTML.
>If I could create my own Xerces parser, and instantiate it with the
>specific standard configuration class that it needs, and then pass it into
>the constructor of the SAXBuilder object, then i don't have to worry about
>a the SAXBuilder object creating a parser on its own, that uses the HTML
>configuration setup by NekoHTML.

I agree this would be a more sensible approach for SAXBuilder. Indeed 
it's what XOM does. However, this would not solve your specific 
problem. Xerces does not allow you to set the parser configuration on 
an specific XMLReader object. The parser configuration is a VM wide 
property. See


   Elliotte Rusty Harold
   elharo at metalab.unc.edu
   Effective XML (Addison-Wesley, 2003)

More information about the jdom-interest mailing list