Thanks Pierre, This helped alot, however I still had to clear out some data structures for this to work.
I.e. some tags were doing database lookups and each iteration was appending the results. I just cleared the container before the lookup. This confused me still because I would have thought that said database container would be created each time the tag got instantiated since it was a data member. Perhaps there is no actual re-instantiation with enablePooling but rather just the lifecycle completed (i.e. doStartTag() -> doEndTag )? Tony --- Pierre Delisle <[EMAIL PROTECTED]> wrote: > Tag reuse is the default behavior for Jasper2 used > in Tomcat 4.1.x. > > Check the docs at > http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jasper-howto.html > > Configuration parameter "enablePooling" determines > whether tag > handler pooling is enabled. It defaults to true. > > The following references will give you better > insight > into "tag-reuse" and should help you fix the > implementation > of your tags so they can behave properly in > containers > that support tag-reuse. > > JSP 1.2: Great News for the JSP Community, Part 2 > [Written by Hans Bergsten. Check the section on > "Tag handler life cycle and instance reuse"] > > > http://www.onjava.com/pub/a/onjava/2001/11/07/jsp12.html > > Taglib Developer Guidelines > [Written by Shawn Bayern. You won't have any more > problems > with tag reuse if you follow these guidelines] > > > http://jakarta.apache.org/taglibs/guidelines.html > > -- Pierre > > > Tony Colson wrote: > > > > I have read various email trails and looked at the > JSP > > 1.2 spec and am still unclear on something > regarding > > custom tags: > > > > I recently upgraded to tomcat 4.1.18 which uses > the > > JSP 1.2 spec and in the case > > > > <custom:TagA> > > <custom:TagB /> > > </custom:TagA> > > > > where TagA re-evaluates the body several times, it > > seems that TagB only gets instantiated once and > > re-used. This doesn't seem right to me (even > after > > reading the specs) especially since it worked with > > previous versions os tomcat using JSP 1.1. I > would > > think that after the TagB.doEndTag() function the > > container would release() it and thus neccessitate > the > > creation of a new TagB object on the next > iteration. > > > > This is important to me because I have underlying > data > > structures which are not behaving correctly > because of > > this. > > > > Is this a bug? Are there ways to "force" it to > always > > instantiate a new TagB? Are there alternate > > containers we can use? > > > > Thanks > > Tony > > > > __________________________________________________ > > Do you Yahoo!? > > Yahoo! Mail Plus - Powerful. Affordable. Sign up > now. > > http://mailplus.yahoo.com > > > > -- > > 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]> > __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
