RE: [RE: SAX2/Java: Towards a final form]
James Layer wrote, > While I share Miles' sentiments regarding legacy baggage, I > believe David's deprecation approach would promote a more > rapid (and smoother) adoption of the new interface (at least > at the company where I work). > > We have abstracted the 'get a parser' process so our app > developers request a parser based (primarily) on > functionality rather than demanding a specific > implementation; I don't think dropping 'extends Parser' should impact on this in any really significant way. Intially I would expect almost all parsers to implement both XMLReader _and_ Parser for SAX1 compatibility, so you'd have a fair breathing space during which casting from the former to the latter would be safe. Actually, one of my worries is that having XMLReader extend a deprecated interface will cause javac/jikes/javadoc to spit out warnings or errors ... not a big deal, perhaps, but a bit of a pain (I'm one of those people who habitually set the 'treat warnings as errors' flag on all my tools ;-). Cheers, Miles -- Miles Sabin Cromwell Media Internet Systems Architect 5/6 Glenthorne Mews +44 (0)20 8817 4030 London, W6 0LJ, England msabin@c... http://www.cromwellmedia.com/ 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/ or CD-ROM/ISBN 981-02-3594-1 Please note: New list subscriptions now closed in preparation for transfer to OASIS.
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