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 22293] New: - JasperLoader prepends fixed package name
Date Mon, 11 Aug 2003 07:50: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=22293>.
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=22293

JasperLoader prepends fixed package name

           Summary: JasperLoader prepends fixed package name
           Product: Tomcat 4
           Version: 4.1.24
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Critical
          Priority: Other
         Component: Jasper 2
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: brettporter@yahoo.com


Recent versions of the Jasper ant task use the directory name for the package so
you can compile a whole tree. That's great.

However, JasperLoader always looks for "org.apache.jsp.JSP_NAME", which results
in (root cause of a servlet exception):
java.lang.NoClassDefFoundError: org/apache/jsp/cookieMonster_jsp (wrong name:
admin/cookieMonster_jsp)
	at java.lang.ClassLoader.defineClass0(Native Method)
	at java.lang.ClassLoader.defineClass(ClassLoader.java:488)
	at java.lang.ClassLoader.defineClass(ClassLoader.java:423)
	at org.apache.jasper.servlet.JasperLoader.loadClass(JasperLoader.java:215)
	at org.apache.jasper.servlet.JasperLoader.loadClass(JasperLoader.java:131)
	at org.apache.jasper.JspCompilationContext.load(JspCompilationContext.java:497)
	at
org.apache.jasper.servlet.JspServletWrapper.getServlet(JspServletWrapper.java:150)

I've tried this out on 4.1.24, and according to CVS the files haven't changed
for 4.1.27 so I imagine it still exists.

Not having a decent way to precompile JSPs is really hurting our production
environment. With the large number of JSPs we have, using the web.xml fragment
is a bit impractical and prevents any recompilation at a later date by the live
server.

Mime
View raw message