ers List [EMAIL PROTECTED]
Subject: Re: more about custam tag life cycle
From: Felipe Schnack [EMAIL PROTECTED]
Sent: Monday, February 03, 2003 10:12 AM
Subject: RE: more about custam tag life cycle
This makes me feel much better :-)
On Mon, 2003-02-03 at 16:09, Tim Moo
The way to look at it is simply that the generated code is going to use
a
tag pool for each distinct class of tags. Unfortunately, there is no
specific action that tells the tag it is being pulled from or being put
back
from the pool.
The page will call release() before it is
-Original Message-
From: Felipe Schnack [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 04, 2003 6:20 AM
To: Tomcat Users List
Subject: Re: more about custam tag life cycle
The way to look at it is simply that the generated code
is going
to use
a
tag pool
Schnack [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 04, 2003 6:20 AM
To: Tomcat Users List
Subject: Re: more about custam tag life cycle
The way to look at it is simply that the generated code
is going
to use
a
tag pool for each distinct class of tags
-Original Message-
From: Felipe Schnack [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 04, 2003 10:59 AM
To: Tomcat Users List
Subject: RE: more about custam tag life cycle
because sometimes we have a tag attribute that isn't
actually an getter/setter attribute
This is NOT true, AFAIK. The same tag instance can be used multiple times
*sequentially* but not *concurrently*. Check out the lifecycle state diagram in the
JSP spec.
--
Tim Moore / Blackboard Inc. / Software Engineer
1899 L Street, NW / 5th Floor / Washington, DC 20036
Phone 202-463-4860
This makes me feel much better :-)
On Mon, 2003-02-03 at 16:09, Tim Moore wrote:
This is NOT true, AFAIK. The same tag instance can be used multiple times
*sequentially* but not *concurrently*. Check out the lifecycle state diagram in the
JSP spec.
--
Tim Moore / Blackboard Inc. /
From: Felipe Schnack [EMAIL PROTECTED]
Sent: Monday, February 03, 2003 10:12 AM
Subject: RE: more about custam tag life cycle
This makes me feel much better :-)
On Mon, 2003-02-03 at 16:09, Tim Moore wrote:
This is NOT true, AFAIK. The same tag instance can be used multiple times
it was intended for cleaning resources like
database connections, etc but I don't see any reason to create yet
another method just for tag reuse
On Mon, 2003-02-03 at 17:00, Will Hartung wrote:
From: Felipe Schnack [EMAIL PROTECTED]
Sent: Monday, February 03, 2003 10:12 AM
Subject: RE: more about custam
-Original Message-
From: Will Hartung [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 03, 2003 2:01 PM
To: Tomcat Users List
Subject: Re: more about custam tag life cycle
[snipped]
This entire problem, at least as I've encountered it,
revolves around not only optional
-Original Message-
From: Felipe Schnack [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 03, 2003 2:12 PM
To: Tomcat Users List
Subject: Re: more about custam tag life cycle
I'm curious, how you get a PageContext when the container
doesn't call setPageContext? Which
On Mon, 3 Feb 2003, Will Hartung wrote:
Date: Mon, 3 Feb 2003 11:00:46 -0800
From: Will Hartung [EMAIL PROTECTED]
Reply-To: Tomcat Users List [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Subject: Re: more about custam tag life cycle
From: Felipe Schnack [EMAIL PROTECTED
I'm curious, how you get a PageContext when the container
doesn't call setPageContext? Which container have this behavior?
What he meant is that it may not call setPageContext *on each
invocation*. It will always be called at least once before doStartTag.
But each invocation shouldn't
-Original Message-
From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 03, 2003 2:37 PM
To: Tomcat Users List
Subject: Re: more about custam tag life cycle
On Mon, 3 Feb 2003, Will Hartung wrote:
Date: Mon, 3 Feb 2003 11:00:46 -0800
From: Will Hartung [EMAIL
-Original Message-
From: Felipe Schnack [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 03, 2003 2:46 PM
To: Tomcat Users List
Subject: RE: more about custam tag life cycle
I'm curious, how you get a PageContext when the container
doesn't call setPageContext? Which
From: Felipe Schnack [EMAIL PROTECTED]
Sent: Monday, February 03, 2003 11:11 AM
Subject: Re: more about custam tag life cycle
I'm curious, how you get a PageContext when the container doesn't call
setPageContext? Which container have this behavior?
I don't see a reason why we should
But each invocation shouldn't get a different pagecontext?
PageContext isn't
something related to request's URL? I guess pagecontext's
functionality isn't very clear to me...
We're talking about reuse within a single page.
Oh, of course, sorry :-)
I think there might be some
-Original Message-
From: Felipe Schnack [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 03, 2003 3:15 PM
To: Tomcat Users List
Subject: RE: more about custam tag life cycle
I think there might be some benefit in clarity to the tag
developer.
The current lifecycle
On Mon, 3 Feb 2003, Tim Moore wrote:
Date: Mon, 3 Feb 2003 14:51:21 -0500
From: Tim Moore [EMAIL PROTECTED]
Reply-To: Tomcat Users List [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Subject: RE: more about custam tag life cycle
Tag reuse is only allowed when the set
Yes, but it can be done... to me seems simpler to change
the spec a little than add even more methods (this tends to
create even more confusion IMHO)
But, to reiterate, there isn't really any kind of useful cleaning you
can do in doFinally that doesn't break the spec in other ways.
2003 14:51:21 -0500
From: Tim Moore [EMAIL PROTECTED]
Reply-To: Tomcat Users List [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Subject: RE: more about custam tag life cycle
Tag reuse is only allowed when the set of attributes that are
used, and their values, are identical
On Mon, 2003-02-03 at 11:00, Will Hartung wrote:
And like I said earlier, it would be nice if there were a pool interface
added to the lifecycle to clean up the tag processing to make optional
properties more portable and easier to write for.
It would be even nicer if the pool were dropped
-Original Message-
From: Felipe Schnack [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 03, 2003 3:56 PM
To: Tomcat Users List
Subject: RE: more about custam tag life cycle
Yes, but it can be done... to me seems simpler to change
the spec a little than add even more
On Mon, 3 Feb 2003, Felipe Schnack wrote:
Hm... so this is standard behavior? release() is called after
doEndTag() in all containers that use pooling?
The release() method is called only after the last time that a tag has
been used, before it gets returned to the pool (in a pooling
On Mon, 3 Feb 2003, Felipe Schnack wrote:
Date: 03 Feb 2003 18:58:17 -0200
From: Felipe Schnack [EMAIL PROTECTED]
Reply-To: Tomcat Users List [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Subject: RE: more about custam tag life cycle
Wow, how tomcat creates a key to store
On Sat, 1 Feb 2003, Joe Tomcat wrote:
Date: 01 Feb 2003 18:38:50 -0800
From: Joe Tomcat [EMAIL PROTECTED]
Reply-To: Tomcat Users List [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Subject: Re: more about custam tag life cycle
On Mon, 2003-02-03 at 11:00, Will Hartung wrote
Joe Tomcat wrote:
arguments. Object pooling is deprecated, except for expensive objects
like db connections.
Are you saying that in general, object pooling is deprecated? In other
words, it's always a bad idea, with the exception of DataSource type pools?
Erik
On Mon, 3 Feb 2003, Erik Price wrote:
Date: Mon, 03 Feb 2003 17:16:54 -0500
From: Erik Price [EMAIL PROTECTED]
Reply-To: Tomcat Users List [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Subject: Re: more about custam tag life cycle
Joe Tomcat wrote:
arguments. Object
28 matches
Mail list logo
