DO NOT REPLY [Bug 17915] New: - Jasper ignores manifest 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=17915>.
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=17915

Jasper ignores manifest classpath

           Summary: Jasper ignores manifest classpath
           Product: Tomcat 3
           Version: 3.2.3 Final
          Platform: All
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Major
          Priority: Other
         Component: Jasper
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: goroh@hotmail.com


The Jasper JSP compiler ignores the classpath declared inside the manifest file 
(MANIFEST.MF) of a web application. The interesting side-effect is that a code 
like this run ok:

Class.forName("full.name.of.a.class");

But this doesn't get compiled by Jasper:

full.name.of.a.class obj;

p.s.: The class "full.name.of.a.class" is inside a JAR referenced at the 
manifest classpath

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