If by "xml filter" you mean SAX's XMLFilter interface...
The simplest approach to writing SAX filters is to just have a single
object implement ContentHandler and pass the filtered data to another
ContentHandler. Our SAXResult is set up to wrap itself around an
sax.ContentHandler, so it can happily talk to a filter of this type.
Unfortunately, sax.XMLFilter is intended to wrap itself around a
sax.XMLReader and to actually be able to control the operation via its
parse() method... so the metaphors collide.
Simplest workaround I can see right now would be to implement a
sax.XMLReader that wraps around a Transformer, and pass that to the
XMLFilter. That feels like it ought to be straightforward, and *might*
actually be something we'd want to ship as a standard Xalan utility
class...
______________________________________
Joe Kesselman, IBM Next-Generation Web Technologies: XML, XSL and more.
"The world changed profoundly and unpredictably the day Tim Berners Lee
got bitten by a radioactive spider." -- Rafe Culpin, in r.m.filk
