Tom Bradford wrote: > > On Thursday, December 13, 2001, at 09:58 AM, Murray Altheim wrote: > > 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?
Last night we tested it against Java 1.3 and 1.4, and it seems that from the command line tools the "xmlns:" is getting taken off of "xmlns:foo" in the server itself. I spit out a serialization of the DOM node before I add it as well as when I get it out, and the node is fine on addition. > > 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. As per your suggestion, I left the vm.cfg directive to use Xindice's DocumentBuilderFactory, but it'd be nice if it worked on any. I'm pretty wiped after yesterday, but I'm going to spend today trying to figure out what's going on on the inside. [It'd be a great help if I could get another snapshot of the CVS tree as it stands right now, as my copy of Xindice is now out of sync with yours. I keep thinking about getting a private ISP account so I can get around our firewall...] Murray ........................................................................... Murray Altheim, Staff Engineer <mailto:murray.altheim@sun.com> Java and XML Software Sun Microsystems, 1601 Willow Rd., MS UMPK17-102, Menlo Park, CA 94025 Ernst Martin comments in 1949, "A certain degree of noise in writing is required for confidence. Without such noise, the writer would not know whether the type was actually printing or not, so he would lose control."
