That's not the only problem.
Expressions (<%= %>) are not converted to Strings
before giving them to methods like encode() or include().
By now I have two examples:
1.)
<jsp:include ..>
...
<jsp:param name="value" value="<%= 1 %>" />
...
</jsp:include>
2.)
<jsp:include page="<%= new StringBuffer("") %>" flush="true"/>
Both ways cause Exception because the value of the expression
is directly used for methods that expect a string.
Given that and other problems that have been mentioned today
I would currently forget about using 4.1.10. (As the last
tc version I used is 4.0.3, I can't make any recommendations)
> -----Urspr�ngliche Nachricht-----
> Von: Dave Townsend [mailto:[EMAIL PROTECTED]]
> Gesendet: Donnerstag, 12. September 2002 16:08
> An: [EMAIL PROTECTED]
> Betreff: tomcat 4.1.10 mishandling nested variables in tags?
>
>
> Just upgraded to 4.1.10 and found that my webapp no longer
> functions. I have
> tracked this down to a tag that uses nested tags. On the old version
> (4.0.4), immediately after the doStartTag call, the variables
> are declared
> for the jsp page, and their values read from the pageContext,
> then the jsp
> content of the tag is executed. On the new version after the
> doStartTag, the
> variables are declared and set to null and only have their
> values updated
> after the jsp content has been executed once. This means that all the
> variables are null on the first run through the tag which as far as I
> understand the spec is not correct.
>
> Is there any fix for this?
>
> Dave
>
> Dave
>
> --
> 404. File not found. Should I fake it? (Y/N)
>
>
>
> --
> To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
