commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 22383] New: - Cause of XmlLoadException swalloed making it hard to debug parse errors
Date Wed, 13 Aug 2003 15:49:01 GMT
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

           Summary: Cause of XmlLoadException swalloed making it hard to
                    debug parse errors
           Product: Commons
           Version: Nightly Builds
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Digester
        AssignedTo: commons-dev@jakarta.apache.org
        ReportedBy: Stefan.Kuehnel@frontis.com


While o.a.c.d.xmlrules.XmlLoadException has constructors taking the Throwable
cause of the exception, this value is never used again.  This makes it rather
hard to debug parse errors in the rule files when using
FromXmlRuleSet#addRuleInstances(). I've created a simple patch that at least
under a 1.4 JDK allows to debug this by calling Throwable.initCause() inside
XmlLoadException.

Mime
View raw message