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=8657>. 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=8657 java.lang.NullPointerException: XRTreeFrag.str(XRTreeFrag.java:280) ------- Additional Comments From [EMAIL PROTECTED] 2002-04-30 17:55 ------- I'm not sure where you think cycles will be burned, but I've rewritten the patch to use the same <condition> code with the existing syntax. Now, this is GUARANTEED not to burn more cycles and be safe. If you want to see if something is wrong, I suggest using assertions, or for backward compatibility, maybe throw a useful and informative exception at the source instead of allowing it to sporatically blow up on a null pointer exception as a SIDE- EFFECT of a real problem. The <default> NullPointerException (no message), in my experience, is one generally thrown by poorly written software. I don't think of Xalan that way, and I don't want others to either. This exception gives more novice users the impression that the software is just plain broken, with no knowlege of what went wrong or how to find out specifically. public String str() { XMLString xmlString = m_dtm.getStringValue(m_dtmRoot); return (null == xmlString) ? "" : xmlString.toString(); }
