RE: DO NOT REPLY [Bug 16749] - Struts EL tag handlers cannot be reused by containers

[Mark Abbott <Ma...@openwave.com>]

Hi Wendy - it's definitely going to be a container
dependent thing, because the problem only crops up 
when the container chooses to take advantage of tag
reuse.  Presumably, not all containers do and the ones
that do may not all do so in the same way.

David's example would definitely cause the problem
in Resin 2.1.6.  If you look at the generated Java
code your container produces for a JSP page (always
an enlightening exercise to try at least once) that
contains loops or other cases where the same tag 
appears more than once on the page with the same set 
of attribute values, you can see what optimizations
the container is using, including possible reuse
of handlers.

       Cheers - Mark

At 11:15 AM 2/4/2003, Karr, David wrote:
>> -----Original Message-----
>> From: Wendy Smoak [mailto:Wendy.Smoak@asu.edu]
>> 
>> David wrote:
>> > I'll also have to build a little test case that clearly demonstrates
>the
>> > symptom.  Is this easily demonstratable in Tomcat?
>> 
>> (Just a user lurking on the dev list here...) I have not seen this
>> behavior
>> in Tomcat 4.1.18.  Has anyone written a tiny webapp that demonstrates
>the
>> problem?  I'm trying not to panic, but I've got a project that depends
>on
>> Struts-EL and JSTL.  I was hoping to see Struts-EL in the final
>release,
>> but
>
>Based on what I understand, if you had a logic-el:iterate loop (or even
>"c:forEach", now) containing a single "html-el:text" component whose
>"value" attribute used an EL expression based on the index variable, the
>first iteration would use the value of the first index, and the second
>iteration would unexpectedly use the value from the first iteration
>(because it wouldn't call the setter).  Is it really this simple?
>
>> > I'll start to put this together, but I won't plan on committing it
>in
>> > the 1.1 timeframe unless we are motivated to want it sooner.
>> 
>> As soon as possible, please!  Is there a consensus on how to fix it
>yet?
>
>As you can see, we're still thinking about it.
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: struts-dev-help@jakarta.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org