The subject? Xindice, XML Namespaces and the Xerces 2 parser.
We've been fairly successful in using the new Xindice (NEE dbXML), which comes delivered with its own jar files for Xerces 1.4.3, xalan 2.0.1. We've replaced some of those existing jars with Xerces 2 and the Xalan 2.2D14. But we have a namespace bug.
I've only testing things against Xerces 1 and Crimson at this point, and the fix the I committed, though it addressed Xerces 1, should have fixed any potential SAX parser problems. Can you tell me whether the documents are ok in the server itself? Or is this happening in the XML:DB SAX event generator?
We're using the Xindice compressed DOM. Is there any way around this?
I'll do some testing with Xerces 2 and see what I can dig up.
-- Tom Bradford - http://www.tbradford.org Developer - Apache Xindice (formerly dbXML) Maintainer - jEdit-Syntax Java Editing Bean
