DO NOT REPLY [Bug 12945] New: - JSP Compilation errors: jars in WEB-INF/lib and classes in WEB-INF/classes not in classpath

[bu...@apache.org]

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=12945>.
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=12945

JSP Compilation errors: jars in WEB-INF/lib and classes in WEB-INF/classes not in classpath 

           Summary: JSP Compilation errors: jars in WEB-INF/lib and classes
                    in WEB-INF/classes not in classpath
           Product: Tomcat 4
           Version: 4.1.12
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Critical
          Priority: Other
         Component: Jasper 2
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: agmartin@grupoburke.com


Hi.

Yesterday I downloaded the tar.gz'ipped version for Tomcat 4.1.12 and 
discovered that the problem showed in bug # 12387 was still present.

The problem is that Jasper compiler still creates an internal classpath with 
a "/" heading that variable which leads to a compilation error for those JSP 
pages that were not yet compiled before.

I implemented a servlet that showed all context properties at runtime and this 
is what I got:

AttributeNames: 
+ Attribute[0]: org.apache.catalina.WELCOME_FILES : [Ljava.lang.String;@dada24
+ Attribute[1]: javax.servlet.context.tempdir : C:\Tomcat-4.1.12
\work\Standalone\localhost\WGFAQ
+ Attribute[2]: org.apache.catalina.resources : 
org.apache.naming.resources.ProxyDirContext@2798e7
+ Attribute[3]: org.apache.catalina.jsp_classpath : /C:/Tomcat-
4.1.12/webapps/WGFAQ/WEB-INF/classes/;C:/Tomcat-
4.1.12/common/endorsed/xercesImpl.jar;C:/Tomcat-
4.1.12/common/endorsed/xmlParserAPIs.jar;C:/Tomcat-
4.1.12/common/lib/activation.jar;C:/Tomcat-4.1.12/common/lib/ant.jar;C:/Tomcat-
4.1.12/common/lib/commons-collections.jar;C:/Tomcat-4.1.12/common/lib/commons-
dbcp.jar;C:/Tomcat-4.1.12/common/lib/commons-logging-api.jar;C:/Tomcat-
4.1.12/common/lib/commons-pool.jar;C:/Tomcat-
4.1.12/common/lib/cos.jar;C:/Tomcat-4.1.12/common/lib/iText.jar;C:/Tomcat-
4.1.12/common/lib/jacob.jar;C:/Tomcat-4.1.12/common/lib/jasper-
compiler.jar;C:/Tomcat-4.1.12/common/lib/jasper-runtime.jar;C:/Tomcat-
4.1.12/common/lib/jdbc2_0-stdext.jar;C:/Tomcat-
4.1.12/common/lib/jndi.jar;C:/Tomcat-4.1.12/common/lib/jt400.jar;C:/Tomcat-
4.1.12/common/lib/jta.jar;C:/Tomcat-4.1.12/common/lib/mail.jar;C:/Tomcat-
4.1.12/common/lib/mysql.jar;C:/Tomcat-4.1.12/common/lib/naming-
common.jar;C:/Tomcat-4.1.12/common/lib/naming-factory.jar;C:/Tomcat-
4.1.12/common/lib/naming-resources.jar;C:/Tomcat-4.1.12/common/lib/servlet.jar

As you can see, attribute #4: "org.apache.catalina.jsp_classpath" starts 
with "/C:...." that can leads to a bug at runtime.

The "jasper-compiler.jar" file, attached in the bug mentioned before, solved 
the problem for Tomcat 4.1.10, but the problem is still in this new release.

That was all. Thanks a lot for your great job.

-----------------------------------------------------------------------
Arturo Garc�a Mart�n

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>