Announcement: SAX2 1999-06-01 alpha release for Java

David Megginson david at
Wed Jun 2 16:19:56 BST 1999

Lars Marius Garshol writes, ironically:

 > Immediate reactions: it looks good, but filters seem to be missing.
 > I think filters really should be in SAX2, for the following reasons:
 >   - the basic filter interface and concept is simple and fundamental
 >   - having a single basic standard for filters is important, as many
 >     different packages will probably/hopefully use them as pluggable
 >     components (MDSAX, SAXON, XSL processors, parsers etc)
 >   - it needs to be done anyway, and doing it in SAX2 saves us an extra
 >     layer of standards

Two responses:

1. Do we need a filter *interface* at all, or can a filter just be a
   class that happens to implement Parser, Configurable,
   EntityResolver, DTDHandler, DocumentHandler, and ErrorHandler?  (In 
   other words, is it enough to set the parent parser/filter in the

2. Actually, just last night I wrote an
   org.xml.sax.helpers.FilterAdapter base class that filters can
   easily be derived from (though they wouldn't have to be); by
   default, it just lets all events sink down to the application, 
   and all configuration bubble up to the parser, but subclasses can
   simply override methods to make changes in either direction.

   I was thinking of including this class in the next SAX2
   pre-release, if people are interested; I can also distribute it
   separately in the mean time.

All the best,


David Megginson                 david at

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at
Archived as: and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:majordomo at the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at

More information about the Xml-dev mailing list