Murray Altheim wrote:
My understanding of this from my own experience, and from Tom Bradford, who
is the Apache Xindice database developer who hacked a patch for it, is that
default namespace declarations are being treated not as namespace declarations
but as attributes, and that rather than returning an empty string the NS is
being returned as null. So, something like:
<xnode:Envelope xmlns:xnode="http://www.apache.org/xnode">
...
</xnode:Envelope>
it's coming back as:
<xnode:Envelope xnode="http://www.apache.org/xnode">
...
</xnode:Envelope>
or not at all, if the application code ends up with a null pointer trying
to process the attributes on <xnode:Envelope>. My hack was to search for
"xmlns:xnode" using the non-namespace-aware DOM method. The parser feature
"namespace-prefixes" should turn on or off event sending on these declarations,
with us using "on" right now. In reality we shouldn't really need to see
their events at all, since the result of them is the namespace mapping itself.
They aren't supposed to be treated as attributes.
also, please see xml.apach.org Bugzilla 5059 part #2
###@###.### 2002-02-06
Tested on Xerces2.0.0. Works fine.
My understanding of this from my own experience, and from Tom Bradford, who
is the Apache Xindice database developer who hacked a patch for it, is that
default namespace declarations are being treated not as namespace declarations
but as attributes, and that rather than returning an empty string the NS is
being returned as null. So, something like:
<xnode:Envelope xmlns:xnode="http://www.apache.org/xnode">
...
</xnode:Envelope>
it's coming back as:
<xnode:Envelope xnode="http://www.apache.org/xnode">
...
</xnode:Envelope>
or not at all, if the application code ends up with a null pointer trying
to process the attributes on <xnode:Envelope>. My hack was to search for
"xmlns:xnode" using the non-namespace-aware DOM method. The parser feature
"namespace-prefixes" should turn on or off event sending on these declarations,
with us using "on" right now. In reality we shouldn't really need to see
their events at all, since the result of them is the namespace mapping itself.
They aren't supposed to be treated as attributes.
also, please see xml.apach.org Bugzilla 5059 part #2
###@###.### 2002-02-06
Tested on Xerces2.0.0. Works fine.