[jdom-interest] Re: XMLOuputter = SAXOutputter + XMLFilter + XMLWriter

[Joseph Bowbeer]

Brett McLaughlin wrote:

> One note: we will never allow the user to pass in their own XMLReader
...

In that case, SAXBuilder could accept an XMLFilter in addition to an
input source, and SAXBuilder could attach the XMLFilter to the XMLReader
it creates from the input source.

A filter could be used to strip whitespace from element content, among
other things.  SAXBuilder could create this filter itself when the user
sets the ignoreElementContentWhitespace property.

A filter could also be used for debugging.  Using an XMLWriter as the
filter would leave the input unchanged, but would output the XML for
inspection.

--
Joe Bowbeer


----- Original Message -----
From: "Brett McLaughlin" <brett.mclaughlin at lutris.com>
To: "Joseph Bowbeer" <jozart at csi.com>
Cc: <jdom-interest at jdom.org>
Sent: Tuesday, October 10, 2000 7:50 AM
Subject: Re: [jdom-interest] Re: XMLOuputter = SAXOutputter + XMLFilter
+ XMLWriter

Joseph Bowbeer wrote:
>
<snip />

One note: we will never allow the user to pass in their own XMLReader;
we have to have certain properties set a certain way; while some are
flexible (like validation), some are completely inflexible (like
namespaces); so we won't ever have that functionality, because we either
(1) lost that control or (2) have to turn it on on their passed in
object, which is deceptive.

We'll get back to the other discussion, I just wanted to clarify our
resons for this ;-)

-Brett