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 28604] New: - JspC should not display the whole stack trace of errors
Date Mon, 26 Apr 2004 17:32:51 GMT
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=28604>.
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=28604

JspC should not display the whole stack trace of errors

           Summary: JspC should not display the whole stack trace of errors
           Product: Tomcat 5
           Version: 5.0.19
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Minor
          Priority: Other
         Component: Jasper
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: petr.jiricka@netbeans.com


1. Set up an application with an Ant script to compile JSPs as recommended at
http://jakarta.apache.org/tomcat/tomcat-5.0-doc/jasper-howto.html
2. Write a JSP which contains erroneous text such that the first phase (JSP ->
Java translation) fails e.g. by including <jsp:include x="50"/> in the page.
3. Compile the application using the Ant script - a Jasper exception will be
reported. This will be reported including the whole Jasper stack trace, which
makes the report unreadable. Just the error message with the location would be
sufficient.

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message