I wouldn't say Xerces handles these "poorly". Rather, it handles them quite "flexibly". As a result, there is a performance penalty. As long as we can be made aware of the performance implications and "high performance" usage scenarios, I think it is the best of both worlds!
Rick Bullotta CTO Lighthammer Software (http://www.lighthammer.com) -----Original Message----- > I was sort of shocked when I first discovered how poorly Xerces > handles setting JAXP DocumentBuilder properties, but from > conversations on this mailing list it's obviously a known problem and > there doesn't seem to be much that can be done about it. Shrug. If anyone's curious what the problem is, here's the explanation [1] I gave the last time this came up. > > Curtiss Howard > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
