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

John Cowan cowan at
Thu Jun 24 22:06:10 BST 1999

David Brownell wrote:

> DocumentSource??  Not a SAX class ... :-)
> If you mean InputSource, the issue I'd raise there is that
> it'd imply that all SAX parsers should be able to accept DOM
> as input.

InputSource, of course.  And I was talking about an extension
(subclass) of InputSource specific to DOM parsing, not changing
(extending) InputSource.  Sorry for the confusion.

Another option is to change InputSource to support a single
additional pair of methods: get/setSourceObject(Object o).
The meaning of this would be specific to the particular parser
and the run-time type of o.
> Why do you not like making that property (dom-node) be read/write,

Essentially because the value of getProperty("dom-node") is a Node,
whereas the argument to setProperty("dom-node", doc) needs to be a
Document.  This is an ugly asymmetry, even though the compiler is
unable to check the type.  Adding a new property
("dom-document") would be better, but not better than overloading
InputSource, which is already meant for the job of specifying
the source.

> beyond that not being what you implemented already?

(heh heh)

John Cowan		cowan at
	You tollerday donsk?  N.  You tolkatiff scowegian?  Nn.
	You spigotty anglease?  Nnn.  You phonio saxo?  Nnnn.
		Clear all so!  'Tis a Jute.... (Finnegans Wake 16.5)

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