Lists Home |
Date Index |
- From: "Bill la Forge" <firstname.lastname@example.org>
- To: "James Clark" <email@example.com>, "XML Dev" <firstname.lastname@example.org>
- Date: Sun, 24 Jan 1999 10:31:28 -0500
From: James Clark <email@example.com>
>> Parser filters are
>> just parsers that have a "parser(Parser)" constructor.
>This makes a lot of sense to me.
>With the setParent(Parser parser) idea, what's a filter supposed to do
>if the app fails to call setParent()? A filter has to have a parent
>Parser. Your suggestion captures this nicely.
Its a problem for MDSAX, which constructs ParserFilters in the other direction,
Sink to Source, rather than Source to Sink.
On the other hand, as long as a ParserFilter can be constructed with a
null Parser, it can be subclassed to subsequently set the parent.
The interface MDSAX in now using is
public interface MDFilter
extends Parser, DocumentHandler, DTDHandler, EntityResolver, ErrorHandler
All of the filters in MDSAX subclass org.ccil.cowan.sax.ParserFilter,
but depend on being able to pass a null Parser parameter in the constructor.
xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:email@example.com the following message;
To subscribe to the digests, mailto:firstname.lastname@example.org the following message;
List coordinator, Henry Rzepa (mailto:email@example.com)