tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 3669] New: - Improve Jasper error reporting (stack traces)
Date Tue, 18 Sep 2001 03:51:41 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=3669>.
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=3669

           Summary: Improve Jasper error reporting (stack traces)
           Product: Tomcat 4
           Version: 4.0 Final
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Jasper
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: craig.mcclanahan@sun.com


Jasper reports all types of validation errors (found by Jasper itself or by a
validator) with a full stack trace.  Considering that the stack trace does not
provide any useful information in this case, and that the error message is
targeted to non-programmers ("page authors"), I suggest that only the validation
error message is displayed for validation errors.

(Submitted by Hans Bergsten <hans@gefionsoftware.com> as part of Bugzilla #3668,
split to a separate bug report for tracking).

Mime
View raw message