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=21974>. 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=21974 Runtime exception from DOM2SAX ------- Additional Comments From [EMAIL PROTECTED] 2003-08-01 19:04 ------- >From the DOM spec: "The attributes nodeName, nodeValue and attributes .... In cases where there is no obvious mapping of these attributes for a specific nodeType (e.g., nodeValue for an Element or attributes for a Comment), this returns null." But according to the DOM spec, the value of a Text node is "content of the text node" -- which I believe should never be null. If I remember discussion in the DOM WG correctly, trying to set it to null is considered a user error; implementations may convert that to "", or may fail immediately, or may accept the null and cause failures later. Implementation dependent, nonportable, "If it hurts when you do that..." We should cross-check this with the DOM WG to make sure I'm remembering it correctly. If _they_ say null is legal, then you're right, we should support it. If they don't -- and I really don't think they will -- you should fix your application code.
