Custom tags can also implement the TryCatchFinally interface. Use the doFinally() method to RE-initialize all instance variables that you don't want to maintain since last usage. I had a problem switching from Tomcat 4.0 to 4.1.
-----Original Message----- From: Tim Moore [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 12, 2002 1:52 PM To: Tomcat Users List Subject: RE: 4.1.12 JSP Tag Lifecycle -- Where to re-initialize tag? Mostly in doStartTag. See http://jakarta.apache.org/taglibs/guidelines.html for more tips. -- Tim Moore / Blackboard Inc. / Software Engineer 1899 L Street, NW / 5th Floor / Washington, DC 20036 Phone 202-463-4860 ext. 258 / Fax 202-463-4863 > -----Original Message----- > From: Will Hartung [mailto:[EMAIL PROTECTED]] > Sent: Thursday, December 12, 2002 2:34 PM > To: Tomcat Users List > Subject: 4.1.12 JSP Tag Lifecycle -- Where to re-initialize tag? > > > In out port of code from 3.2 to 4.1, we're encountering some > problems with how Tomcat reuses our tags. > > I looked at the code, and TagHandlerPool does not call the > 'release' method of the tag unless the pool is full (this is > within the reuse method). > > My question, then, where is the appropriate place to > re-initialize internal properties for a jsp tag? > > The life cycle diagram doesn't really have a "precise" place > to reinitialize the content to their defaults, so I'm curious > where others are putting this kind of code. > > Regards, > > Will Hartung > ([EMAIL PROTECTED]) -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
<<attachment: winmail.dat>>
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
