https://issues.apache.org/bugzilla/show_bug.cgi?id=56516
--- Comment #3 from Konstantin Kolinko <knst.koli...@gmail.com> ---
Re: r1594715
I think this report is invalid.
In JSP specification (JSP2.3MR.pdf) there are three occurrences where an action
defines a variable:
1. A <jsp:useBean> action (chapter JSP.5.1)
2. A custom action returning a VariableInfo with declare=true from its TEI
class
3. A tag file declaring a variable declare=true
For 1. there is explicit example on visibility of declared variables. See
ch.JSP.5.1 "<jsp:useBean>" page "1-95" (133 of 594)/
For 2.,3. declaration of variables is illustrated in ch.JSP.9.4.4 "Actions"
page "1-196" (234 of 594). It also says:
> "Their visibility is affected by other constructs, for example scriptlets."
For 3. in ch.JSP.8.5.3 "The variable Directive" on page "1-183" (221 of 594)
description of "declare" attribute says:
> "declare (optional) Whether the variable is declared or not in the
> "calling page/tag file, after this tag invocation. true is the
> "default."
I see no provision for declaring the variables prematurely.
Also Re: r1594715
1) I see no test example
2) I am certain that it is wrong to prematurely declare NESTED variables.
Regarding NESTED variables, iff <c:forEach> declared NESTED variables I expect
the following to fail with r1594715 because of duplicate declaration of "i":
[[[
<c:forEach var="i" begin="1" end="10"> ${i} </c:forEach>
<% for (int i=0; i < 10; i++) {
out.println(i);
}
%>
]]]
Actually JSTL tags do not work that way. They expose information only as JSP
scoped attributes. They do not expose them as scripting (java) variables.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
