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-04 13:06 ------- Parse has to scan characters anyway, so detecting it there doesn't impose significant overhead. Checking for it in the DOM APIs would, which is why the DOM didn't require checking. Individual implementations are free to do so or not do so as they prefer. Fix your application code, or create a DOM with tighter checking that you can use in untrusted environments where the overhead of parameter checking is justified. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
