On Tue, 4 Feb 2003, David M. Karr wrote:
> Date: 04 Feb 2003 20:49:24 -0800 > From: David M. Karr <[EMAIL PROTECTED]> > Reply-To: Struts Developers List <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: Re: DO NOT REPLY [Bug 16749] - Struts EL tag handlers > cannot be reused by containers > > >>>>> "David" == David Karr <Karr> writes: > > >> -----Original Message----- > >> From: Wendy Smoak [mailto:[EMAIL PROTECTED]] > >> > >> David wrote: > >> > I'll also have to build a little test case that clearly demonstrates > David> 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 > David> the > >> problem? I'm trying not to panic, but I've got a project that depends > David> on > >> Struts-EL and JSTL. I was hoping to see Struts-EL in the final > David> release, > >> but > > David> Based on what I understand, if you had a logic-el:iterate loop (or even > David> "c:forEach", now) containing a single "html-el:text" component whose > David> "value" attribute used an EL expression based on the index variable, the > David> first iteration would use the value of the first index, and the second > David> iteration would unexpectedly use the value from the first iteration > David> (because it wouldn't call the setter). Is it really this simple? > > After trying to set up a test case for this, I'm finding I cannot repeat it > with Tomcat. I already had a test case for this, unknowingly. I'm using > Tomcat 4.1.18(LE/JDK14). Is there something I have to do to "enable" this > feature of reusing tag handlers? Tomcat currently implements pooling, but it's not necessarily as aggressive about reuse as it could be. But one thing to double check is in "$CATALINA_HOME/conf/web.xml" -- the "enablePooling" init parameter on the JSP servlet needs to be set to true (which is the default). Craig --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
