[jdom-interest] Feature Request
Jeremy.Prellwitz at siras.com
Jeremy.Prellwitz at siras.com
Thu Feb 19 18:52:44 PST 2004
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.
-jeremy
"Chris B."
<chris at tech.com.a
u> To
Jeremy.Prellwitz at siras.com
02/19/2004 05:55 cc
PM jdom-interest at jdom.org
Subject
Re: [jdom-interest] Feature Request
As much as I think its a good idea, how would it help you directly,
since NekoHTML doesn't seem to conform to XMLReader? (Which seems to be
its problem).
Jeremy.Prellwitz at siras.com wrote:
>This is what I was trying to describe, just without mentioning it as
>specifically/consisely as you just did. I wouldn't have brought up my own
>little issue if I didn't think that passing in your own XMLReader instance
>could offer usefulness to others. It seems like a simple enough change to
>the SAXBuilder.java class, and conincidently, it would smooth out my code
a
>little bit. :-)
>
>-jeremy
>
>
>
>
>
>>It seems to me that supplying your own XMLReader is a sensible enough
>>activity that it deserves a proper method or constructor in SAXBuilder
>>to pass it in.
>>
>>
>
>
>
>
>
> "Chris B."
> <chris at tech.com.a
> u> To
> Jason Hunter <jhunter at xquery.com>
> 02/19/2004 05:00 cc
> PM Jeremy.Prellwitz at siras.com,
> jdom-interest at jdom.org
> Subject
> Re: [jdom-interest] Feature Request
>
>
>
>
>
>
>
>
>
>
>Jason Hunter wrote:
>
>
>
>>Sounds like nekohtml is being a Bad Citizen, but I think you can do
>>exactly what you want by subclassing SAXBuilder and overriding
>>createParser().
>>
>>
>
>
>It seems to me that supplying your own XMLReader is a sensible enough
>activity that it deserves a proper method or constructor in SAXBuilder
>to pass it in.
>
>
>
>
>_______________________________________________
>To control your jdom-interest membership:
>http://lists.denveronline.net/mailman/options/jdom-interest/youraddr@yourhost.com
>
>
More information about the jdom-interest
mailing list