DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1319>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1319 xsl:copy handles namespaces incorrectly [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Additional Comments From [EMAIL PROTECTED] 2001-10-05 09:36 ------- The Namespaces In XML spec explicitly says that namespaces are signified as URIs (the empty string is not a valid URI), and that xmlns="" is interpreted as a request to undefine the default namespace, _not_ to set it to "". So from that point of view, null really is the right answer. That's certianly how the DOM spec interpreted this, and I think it's how DTM handles it. However, it looks like SAX does expect "", given the javadoc for ContentHandler.startElement. I believe our serializer actually tolerates both, but since someone might want to plug our SAX stream into something else, I'll drop a patch into ClonerToResultTree. We may or may not need similar patches at other calls to startElement().
