Hi Edwin, >of those classes is that each parser implementation should provide a >default parser instance when the SAX "driver" property is not set, >instead of failing. The newer versions of SAX point this out and make >it easy to modify the code to do so. What earlier versions of parsers >typically did was to not make any modifications to the SAX code and so >if the "driver" property was not set, then the app would get an >exception. Something to add to the todo list
No need; this is done already in Xerces2. The thrust of my concern was to ensure that folks can use XMLReaderFactory and co. to determine the kind of SAXParser they get back, just as Andy has allowed people to use JAXP interfaces and still tailor the sort of parser that gets returned to their needs. Looks like this should work so it's not a concern. Cheers, Neil --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
