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 [EMAIL PROTECTED]  2002-10-01 19:46 -------
I do believe the problem stated in 13132 does apply to your situation. Remember
13132 started out with this code fragment:

<% if (condition) { %>
<i18n:message key="some.key" id="myID"/>
<% } else { %>
<i18n:message key="some.other.key" id="myID"/>
<% } 
%>

which is exactly what you are trying to do. The purpose of the example I gave in
the evaluation of 13132 is to show that some developers may rely on AT_END
variables to be declared after the call to the tag handler's doEndTag() method,
so that a nested tag may declare an AT_END variable of the same name, but with a
different type than an AT_END variable declared by the enclosing tag.

Would the workaround that I suggested for bug 13132 work for you, i.e., do
something like the following:

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

I am little reluctant adding a configuration property for this, as it would not
be portable across containers.

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to