Hey Jasper gurus-- is this a bug?
I have this JSP example (note the exclamation point):
<%! /* This method returns null-- Jasper should probably give a
compiler
error, since this is a dangerous pitfall for JSP developers.
*/
private PageContext getPageContext() {
return pageContext;
}
%>
<html>
<body>
<pre><%= getPageContext() %></pre>
</body>
</html>
Should this example page compile properly? 'pageContext' is null (from the
method only) when I run it-- I thought it would be nice for
a) Jasper to give a compiler error when it sees such a dangerous reference.
-OR-
b) pageContext to not be null from the JSP method
It seems the member is inherited from 'protected PageContext pageContext' at
org/apache/jasper/runtime/HttpJspBase.java:81
I am reporting against Tomcat 4.0.3 Final binaries and source.
Please let me know if I should file a report on nagoya.apache.org/bugzilla,
and if so, what component to file it against. (Jasper? Jasper 2?)
Thanks,
Steve
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
