[jdom-interest] Feature Request

Jeremy.Prellwitz at siras.com Jeremy.Prellwitz at siras.com
Fri Feb 20 08:00:51 PST 2004

Yes, i know there are work-arounds, which i am using right now.  My only
point is that I thought there would be value added by adding the
functionality to pass in your own XMLReader, or Xerces configuration class.

I think this topic has probably been discussed enough, i suppose its up to
the commiters, if they actualy want to add this to the next release.  I'm
brand new to making dev-list postings/requests, and i don't want to wear
out my welcome. :-)


             "Richard Cook"                                                
             <rpc at etlsolutions                                             
             .com>                                                      To 
             Sent by:                  <jdom-interest at jdom.org>            
             jdom-interest-adm                                          cc 
             in at jdom.org                                                   
                                       RE: [jdom-interest] Feature Request 
             02/20/2004 07:51                                              

Isn't it just the default that's system wide, and
SAXParser(XMLParserConfiguration) constructor can be used for a
Also http://www.apache.org/~andyc/neko/doc/html/usage.html has some info on
not letting neko affect every xerces parser instance.

-----Original Message-----
From: jdom-interest-admin at jdom.org [mailto:jdom-interest-admin at jdom.org] On
Behalf Of Elliotte Rusty Harold
Sent: 20 February 2004 13:37
To: Jeremy.Prellwitz at siras.com
Cc: jdom-interest at jdom.org
Subject: Re: [jdom-interest] Feature Request

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)


To control your jdom-interest membership:


To control your jdom-interest membership:

More information about the jdom-interest mailing list