SAX2 RFD: Inheritance vs. Modification vs. Amalgamation
donpark at quake.net
Wed May 19 22:11:45 BST 1999
> 2. Add the methods to org.xml.sax.Parser, and require applications to
> catch NoSuchMethodException when using the new methods, in case
> they're concerned about what version they're dealing with.
> PRO: - doesn't limit options for subclassing in the future
> CON: - very difficult to write adapters for existing SAX 1.0
> drivers (slower acceptance and implementation of SAX2)
> - can cause unexpected behaviour at deployment time, unless
> the application designer knows to catch
I prefer #2 combined with a helper class to ease some of the pain.
If the client supports SAX2 only, then they can invoke Parser directly.
If the client supports both SAX and SAX2, then they can invoke the static
helper methods in the helper class which handles things like
They should be passing an instance of the parser to the static helper
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/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)
More information about the Xml-dev