Internet)
[mailto:[EMAIL PROTECTED]
Sent: Thursday, August 07, 2003 10:28 PM
To: Tomcat Users List
Subject: RE: Custom Tag Lib
Shawn,
I ran into this problem as well when switching from 4.0 to 4.1. I think it
has something to do with 4.1 pooling and re-using tag objects. What I did
in all of my
:[EMAIL PROTECTED]
Sent: Friday, August 08, 2003 8:06 AM
To: Tomcat Users List
Subject: RE: Custom Tag Lib
It would be best if you went a rewrote your tags not to require release
to be called. That change will also bring you in-line with the jsp
spec. These links might help:
http://www.onjava.com/lpt
Shawn,
I ran into this problem as well when switching from 4.0 to 4.1. I think it
has something to do with 4.1 pooling and re-using tag objects. What I did
in all of my doStartTag(), doAfterBody(), etc... methods was manually call
release() to reset the data in the tags like so:
public int
Yikes, calling release() in doStartTag() stops any state being
accessible to child (body) tags. That would kill our custom iterator tags.
You could have your tags implement the TryCatchFinally interface,
instead. That way you'll have a chance to reset state before reuse:
Users List
Subject: RE: Custom Tag Lib
Hi Shawn,
Actually, I wasn't aware that there was an option to disable it. When I
figured out what was happening, I went ahead and handled it in my code. No
telling how other application servers might handle it. If you're only going
to be deploying on Tomcat
Users List
Subject: RE: Custom Tag Lib
Mr. Mezick:
From what I'm gathering, the release should not be
implimented to reset the
data and classes used by a tag, but only for things like
closing files and
db connections? Just to make sure I'm thinking about this
properly
TryCatchFinally is probably not only cleaner, but is also more spec
friendly.
--Angus
-Original Message-
From: Mike Cherichetti (Renegade Internet)
[mailto:[EMAIL PROTECTED]
Sent: Friday, August 08, 2003 12:42 PM
To: Tomcat Users List
Subject: RE: Custom Tag Lib
I should have
save you some
time, but you still might want to handle it in your code to get better
performance.
Mike
-Original Message-
From: Shawn Zernik [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 07, 2003 11:41 PM
To: Tomcat Users List; [EMAIL PROTECTED]
Subject: RE: Custom Tag Lib
Mike
.
Mike
-Original Message-
From: Jon Wingfield [mailto:[EMAIL PROTECTED]
Sent: Friday, August 08, 2003 5:08 AM
To: Tomcat Users List
Subject: Re: Custom Tag Lib
Yikes, calling release() in doStartTag() stops any state being
accessible to child (body) tags. That would kill our custom iterator
SimpleTag is part of JSP2.0 which is in tomcat5. AFAIK, there is no simpletag
for jsp1.2 (tomcat4)
More info on tag pooling:
http://jakarta.apache.org/tomcat/faq/misc.html#tagpool
http://jakarta.apache.org/tomcat/faq/misc.html#tagbroken
-Tim
Shawn Zernik wrote:
Mike:
I can't resolve that
-Original Message-
From: Shawn Zernik [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 07, 2003 11:41 PM
To: Tomcat Users List; [EMAIL PROTECTED]
Subject: RE: Custom Tag Lib
Mike:
Thanks so very much... I saw their is a config option in
the Jasper to
turn off tag pooling. do you
11 matches
Mail list logo
