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 21390] - Incorrect code generated by the jsp compiler
Date Tue, 22 Jul 2003 01:27:01 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=21390>.
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=21390

Incorrect code generated by the jsp compiler





------- Additional Comments From ecarmich@alumni.rice.edu  2003-07-22 01:27 -------
The following JSP page also generates a compile error when added to Roshan's 
sample application:

<%@ taglib uri="/test" prefix="test" %>

<%
/*
%>
<test:test/>
<%
*/
%>
<test:test1/>

The problem with both these pages is that the logic in 
ScriptingVariableVisitor that determines which scripting variables each custom 
tag declares doesn't consider the effect of the page's scripting elements.  
That can be fixed, but on the other hand I can't find anything in the JSP 2.0 
spec which says scripting variable declarations are optional, except in the 
trivial case where the variable would not be accessible in the context in 
which it were declared, which doesn't apply here.  Should Japser perhaps just 
declare all scripting variables, and leave it to page and tag library authors 
to prevent conflicts?

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


Mime
View raw message