On Sat, 12 Oct 2002, Stefan wrote:
> I just decided recently to finally look at using taglibs. For the last
> couple of years I have been fine with using <%= %> that processed bean
> methods that return strings. But now seeing how many taglibs there are out
> there, I decided it was time to jump in. Now if I can figure out why I can't
> use the results of a taglib as an arguement for a method in a Java bean?
>
> Example:
>
> <%= my.myMehtod(<c:out value='${value.location}'/>);%>
Effectively what you have here is a piece of the JSTL inside Java scope.
<%= ... %> has the ... being Java code, not JSP. At least that's how I
look at it, the bug in String taglib shows that I've still got some
understanding to do on the Taglib lifecycle.
I'd not thought of the order in which scriptlets/taglibs are executed, I
think because I tennd to use them by instinct/experience and don't think
of the why's etc. Hopefully someone else knows the spec and
realities better.
> What I have noticed is that scriptlets seem to get ouputted before taglibs
> ... or the reverse, I forget which way. What ever it may be, the above
> sample code would have the tag been passed as a string; that is "<c:out
> value='${value.location}'/>" instead of the output of the tag. So I guess
> scriptlets gets process before, right?
>
> Thanks again,
>
> Stef
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
