Cart
[Home] [By Thread] [By Date] [Recent Entries]
Miles Sabin <msabin@c...> writes:
> Hmm ...
> I _really_ don't like the way that the SAX1 and SAX2 stuff is
> all mixed up together, particularly since most of SAX1 is
> deprecated.
Of the core classes and interfaces, only Parser, AttributeList,
DocumentHandler, and HandlerBase (which is really a helper anyway) are
deprecated. All of the rest -- InputSource, Locator, EntityResolver,
DTDHandler, ErrorHandler, SAXException, and SAXParseException -- are
left untouched.
> Like it or not SAX2 is a completely new API, so why not leave SAX1
> untouched (ie. no @deprecated's) and have a completely fresh
> org.xml.sax2.* tree?
Actually, most of it is the same. For the C++ implementation,
obviously, we won't bother with the deprecated interfaces and classes.
> And I still think there needs to be a SAX2 equivalent of
> ParserFactory ... bizarrely it's easier to create a SAX1
> Parser in an implementation independent way than it is to do
> the same for an XMLReader. A couple of people volunteered to
> try out the XMLReaderImplementations stuff I put together, and
> hopefully they'll be able to give some feedback on it to this
> list.
I haven't ruled out putting something in before SAX2 goes final, but
it has to be very small and very simple.
Thanks for the comments, and all the best,
David
--
David Megginson david@m...
http://www.megginson.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
Unsubscribe by posting to majordom@i... the message
unsubscribe xml-dev (or)
unsubscribe xml-dev your-subscribed-email@your-subscribed-address
Please note: New list subscriptions now closed in preparation for transfer to OASIS.
|
