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=22054>. 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=22054 It's possible to create a text node with a null byte, resulting in erratic behavior ------- Additional Comments From [EMAIL PROTECTED] 2003-08-01 14:13 ------- The DOM spec doesn't forbid intensive checking of every argument... but doesn't require it since doing so would impose severe performance costs which are -- in most cases -- entirely unnecessary. I'd suggest you write a value-checking utility in your application code and call that before calling the DOM methods. That would let you apply this check only where it's actually needed, and would have the further advantage of giving you better control over how to recover should a problem be detected. Or: If it hurts when you do that, don't do that; null is not a valid XML character. I'd recommend marking this as INVALID, or knocking severity down to Enhancement since if we were going to do it in Xerces the right solution would be a separate DOM implementation for use in untrustworthy contexts. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
