genuinely conformant parsers written in Java is very small. Up till now Xerces had been clearly the best. Possibly, if I don't find a better alternative, and if there's no simple way to turn Xerces into a conformant parser, then I will have to fork it. :-(
I think you're being a little melodramatic, Elliotte. ;)
As Michael stated, there is an easy mechanism to override which parser configuration is used in Xerces by default. And this would affect all Xerces instances in the JVM (or custom class-loaded sandbox, if you want to use this mechanism more than once in the same JVM), including the parser instances created with JAXP.
I use the same mechanism in NekoHTML to swap out the Xerces standard parser configuration with one capable of parsing HTML. It's just an added Jar file that contains the META-INF/services document queried by Xerces.
-- Andy Clark * [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
