Michael Glavassevich wrote:
Unless you want to enable XInclude processing, plug-in a schema validator or reliably reset the parser to the configuration it had when it was created. If you want to do these things, SAX2 alone isn't sufficient.
That can all be done with XMLReader and XMLReaderFactory. That's what feature and properties are for. SAXParser/SAXParserFactory is flawed at its core. and backwards compatibility requirements mean that it cannot be fixed. A stake should be driven through its heart, its head chopped off, garlic stuffed in its mouth, and the whole rotting corpse burned. The design flaws in these two classes waste thousands of hours of programmer time around the world every year. I have lost count of how many times I've had to fix bugs in people's code because they used SAXParser and SAXParserFactory in the obvious, natural, and thoroughly wrong way; and this includes code shipped by Apache written by programmers who you really would have thought would have known where the pitfalls lay.
SAXParser and SAXParserFactory should be deprecated and no further development should be done on them. They haven't been necessary for half a decade, and their continued existence is a blot on XML and Java.
-- Elliotte Rusty Harold [EMAIL PROTECTED] XML in a Nutshell 3rd Edition Just Published! http://www.cafeconleche.org/books/xian3/ http://www.amazon.com/exec/obidos/ISBN=0596007647/cafeaulaitA/ref=nosim --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
