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 3617] New: - "null" in JasperException
Date Fri, 14 Sep 2001 15:55:25 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=3617>.
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=3617

           Summary: "null" in JasperException
           Product: Tomcat 4
           Version: Nightly Build
          Platform: Sun
        OS/Version: Solaris
            Status: NEW
          Severity: Minor
          Priority: Other
         Component: Jasper
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: mak-apache-bugzilla@greenhills.co.uk


A JSP <%@ page import %> problem in an error page caused an error message:

  org.apache.jasper.JasperException: Unable to compile class for 
  JSPnull/crab/mak/tomcat/work/localhost/example/error$jsp.java:4:
  Class ... not found in import.

Note the "null"; That is returned by findMapping() to getJspLineErrors()
in jasper/src/share/org/apache/jasper/compiler/Compiler.java

Given that null is a possible result for findMapping(), getJspLineErrors()
should check for it before using the value. But I expect findMapping()
was actually supposed to find some mapping for this line. I haven't had the
time to look into this further.

Mime
View raw message