Re: Xindice namespace problem

2001-12-13 Thread Tom Bradford
Tom Bradford wrote: > > On Thursday, December 13, 2001, at 12:16 PM, Tom Bradford wrote: > > It looks as though the Xerces 2 SAX parser is reporting the namespaceURI > > for xmlns: as null. I don't know if this is legal or not... One > > would think it should be reported as an empty string, but

Re: Xindice namespace problem

2001-12-13 Thread Tom Bradford
On Thursday, December 13, 2001, at 12:16 PM, Tom Bradford wrote: It looks as though the Xerces 2 SAX parser is reporting the namespaceURI for xmlns: as null. I don't know if this is legal or not... One would think it should be reported as an empty string, but I'll follow up with the Xerces team.

Re: Xindice namespace problem

2001-12-13 Thread Tom Bradford
Murray Altheim wrote: > 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

Re: Xindice namespace problem

2001-12-13 Thread Murray Altheim
Kimbro Staken wrote: > > On Thursday, December 13, 2001, at 11:26 AM, Murray Altheim wrote: > > > > > 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 seriali

Re: Xindice namespace problem

2001-12-13 Thread Kimbro Staken
On Thursday, December 13, 2001, at 11:26 AM, Murray Altheim wrote: 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 wel

Re: Xindice namespace problem

2001-12-13 Thread Tom Bradford
On Thursday, December 13, 2001, at 11:26 AM, Murray Altheim wrote: 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 we

Re: Xindice namespace problem

2001-12-13 Thread Murray Altheim
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,

Re: Xindice namespace problem

2001-12-13 Thread Tom Bradford
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 thos

Xindice namespace problem

2001-12-13 Thread Murray Altheim
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 hav