Next Round

[Bill la Forge]

> > Or we could just redefine setDocumentHandler so that LexicalHandler is
> > automatically set if the given DocumentHandler implementation also
> > implements that interface.  The two interfaces are strongly related after
> > all.
>
>That's a bit Java-specific -- not all languages actually allow you to
>dynamically determine this sort of thing at runtime.


Having LexicalProcessor extend DocumentHandler would be a significant aid
in developing a generic filter framework, as it reduces the number of interface combinations
that need to be supported. (Filter structures for Document events likely being the same
structure needed to support Lexical events.)

One way to avoid being too Java-specific would be to support methods for each interface,
but adopt the convention that calling either method nullifies the effect of previous calls to
both methods.

Bill


xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)