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=41182>.
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=41182
Summary: Jasper ignores JspServlet's 'classpath' init param
Product: Tomcat 5
Version: 5.5.20
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: Jasper
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: werner.loibl@gmail.com
JspServlet describes and reads a servlet init parameter 'classpath'.
Documentation says:
"classpath - What class path should I use while compiling generated servlets? By
default the classpath is created dynamically based on the current web application."
Current behaviour is that the configured classpath is only considered if no
classpath is configured as servlet context attribute.
---JspRuntimeContext:335----
String cp = (String) context.getAttribute(Constants.SERVLET_CLASSPATH);
if (cp == null || cp.equals("")) {
cp = options.getClassPath();
}
It seems that when running within tomcat the context attribute is usually
present and therefore the classpath from the servlet init parameter is not
considered.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
|