You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by bu...@apache.org on 2004/02/28 02:28:39 UTC
DO NOT REPLY [Bug 22383] -
Cause of XmlLoadException swalloed making it hard to debug parse errors
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=22383>.
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=22383
Cause of XmlLoadException swalloed making it hard to debug parse errors
------- Additional Comments From simon@ecnetwork.co.nz 2004-02-28 01:28 -------
Hmm.. the code is a bit odd, isn't it? The XmlLoadException class takes a cause
parameter, and stores it in a private member variable, but never does anything
with it and never provides any methods to access it.
How about we add a (one-line) getCause() method to this class? This would be
api-compatible with java1.4 exceptions, but allow the class to work the same on
all platforms. This solution is explicitly mentioned in the Jdk1.4 javadocs for
Throwable.getCause() as a good solution for pre-1.4 exceptions.
Or have I missed something?
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org