"Timothy M. Dean" wrote: > > I'll have to look into it further before I can diagnose exactly what is > going on. I am working with the latest Xindice code from CVS, and I was > still encountering the problem. When I was looking at some other > namespace problems, it looked to me that something wierd was going on in > the Xalan DefaultPrefixResolver class, but it definitely could be > somewhere deeper (such as in the Xerces 2 code). > > I have temporarily worked around the problem by not using default > namespaces in my node selection for XUpdates. This is an easy enough > workaround for now, but I wanted to look into the problem a bit deeper > when I get the chance. Knowing which Xalan and/or Xerces code bases are > currently included in the Xindice CVS repository would be helpful for > me...
Well, from what it sounds like this is exactly the same bug we were dealing with, where the namespace prefix was being dropped off of the namespace declaration. Be sure to try both true and false on Xerces 2 parser configuration for the property http://xml.org/sax/features/namespace-prefixes I can't remember which way this should be set off the top of my head, but it's the one controlling whether or not the SAX parser receives the namespace declarations as attributes or not. I thought Tom had provided a workaround in Xindice (until this gets fixed more properly in Xerces). If it turns out to be something in Xalan as well, please let us know. Murray ........................................................................... Murray Altheim <mailto:murray.altheim@sun.com> XML Technology Center, Java and XML Software Sun Microsystems, Inc., MS MPK17-102, 1601 Willow Rd., Menlo Park, CA 94025 Corporations do not have human rights, despite the altogether too-human opinions of the US Supreme Court.
