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 13081] - ScriptingVariableVisitor#setScriptingVars does not account for scriptlet scopes
Date Tue, 01 Oct 2002 18:21:22 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=13081>.
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=13081

ScriptingVariableVisitor#setScriptingVars does not account for scriptlet scopes





------- Additional Comments From craig.setera@kingland.com  2002-10-01 18:21 -------
This problem is mostly unrelated to bug 13132 referenced in the last comment. 
This is extremely easy to reproduce and I believe still well within the scope of
the JSP specification.  Take for instance a very simple snippet of JSP code:

<prefix:outerTag>
<prefix:innerTag id="x" />
<prefix:innerTag id="x" />
</prefix:outerTag>

This snippet will work fine in 4.1.x, but with one minor modification the page
will no longer compile.

<prefix:outerTag>
<% if (true) { %>
<prefix:innerTag id="x" />
<% } %>
<prefix:innerTag id="x" />
</prefix:outerTag>

We have this in our pages.  Even in our pages that are made up almost entirely
of tags, we have conditional statements like this.  We feel that they are
REQUIRED because the overhead of the generated code required to invoke a tag is
too high when compared to a simple conditional check such as this.  

As long as scriptlets are supported in JSP, this construct should be handled
correctly by Jasper or at least be made to conditionally handle this situation
via a configuration mechanism as I suggest in the original bug comments.  I
would be more than willing to put together a patch for this configurable
support, if it would be accepted by the development team.  Otherwise, it isn't
worth my time to build a patch and be constantly out of sync with the base
Tomcat codebase.

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


Mime
View raw message