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] - JspC should not display the whole stack trace of errors
Date Wed, 12 May 2004 22:59:35 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





------- Additional Comments From jan.luehe@sun.com  2004-05-12 22:59 -------
- Include full path of the JSP that contains the error:

  Done!

- Avoid including a link to line number in build.xml:

  'ant' is adding the build.xml line number when catching the exception
  thrown by JspC.execute(). I don't think there is anything we can do to
  avoid this.

- Text "org.apache.jasper.JasperException" is unnecessary:

  The exception class name is printed by JasperException.toString(),
  which is inherited from java.lang.Throwable.toString():

    public String toString() {
        String s = getClass().getName();
        String message = getLocalizedMessage();
        return (message != null) ? (s + ": " + message) : s;
    }

  We could override JasperException.toString() to suppress the
  exception class name and just output the exception message.
  I agree the exception class name is redundant when using JspC,
  but it is useful info when compiling via the JspServlet.
  Won't be changed. :)

---------------------------------------------------------------------
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