Altova Mailing List Archives

Re: ModSAX (SAX 1.1) Proposal

From: James Clark <jjc@------.--->
To: xml-dev@--.--.--
Date: 2/23/1999 5:36:00 AM
Don Park wrote:

> >parser.setHandler("org.xml.sax.namespace", nsHandler);
> >
> >Now the handler org.xml.sax.namespace will need to be of some specific
> >type, org.xml.sax.NamespaceHandler, say.  What needs to be checked is
> >that nsHandler is of type org.xml.sax.NamespaceHandler.  Using
> >ModHandler doesn't do that.
> It does if org.xml.sax.NamespaceHandler implements ModHandler.
> public class NamespaceHandler implements ModHandler {}
> ModParser parser;
> try
> {
>     parser.setHandler("org.xml.sax.namespace", new NamespaceHandler());
> }
> catch (Exception ex)
> {}

My point is it doesn't stop you doing:

public class PingHandler implements ModHandler { }

ModParser parser;

parser.setHandler("org.xml.sax.namespace", new PingHandler());

Declaring the second argument to be of type ModHandler doesn't ensure
that it is of the correct type.  It's not type-safe.


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


These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.