RE: SAX2 RFD: Inheritance vs. Modification vs. Amalgamation
I'd go for an amalgam of (1) and (3): define a new interface Parser2 that is forwards-compatible from Parser but *doesn't* extend it. Give the supplier the choice of implementing either or both interfaces (in the same or different classes). The user decides which interface he's going to use and selects a product that supplies it. This makes it difficult to write a client application that will work directly with either interface, but the availability of adapters (in both directions) should mean this isn't a problem. The fact that Parser2 doesn't extend Parser will ensure that the old Parser interface eventually falls into disuse. Mike Kay > > 1. Create a new interface, org.xml.sax.Parser2, that extends > org.xml.sax.Parser. > > 3. Create a separate interface org.xml.sax.ParserProps (or something > like that), and require SAX2 drivers to implement both interfaces. > xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i... 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@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...)
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format