DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=28762>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=28762 NullPointerException in TreeWalker ------- Additional Comments From [EMAIL PROTECTED] 2004-05-04 14:16 ------- Take that up with the Xerces folks. Purely personal reaction, as an ex-DOM WG-member: Unfortunately DOM Level 1 applications are still supported by the W3C, so this is a case of "deprecated for uses other than backward compatability" -- and even Java doesn't have a good way of expressing that. Also, you'd be trying to deprecate an implementation method without deprecating the interface it's generally invoked through, which would be of limited utility. So I'm afraid this becomes a matter of educating users. I believe this topic is covered in the DOM FAQ (http://www.w3.org/DOM/faq.html), which really should be Required Reading for all DOM users. (If not, it certainly should be.) But as I say, the DOM's design and implementation are pretty far outside Xalan's scope. There's a pending wishlist item for Xalan to add an adapter which would let us try to support level-1 DOMs, however unreliably. We've tried that in the past, before DOM Level 2 established itself. I don't recommend spending time on that right now, given the pending proposal to cut over to XDM and given that DOM Level 1 is rapidly Going Away except as a pitfall for newbies to fall into. Please confirm that fixing your code to produce Level 2 DOM nodes solves the problem, so we can close this bug report. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
