tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Craig R. McClanahan" <>
Subject Re: more about custam tag life cycle
Date Tue, 04 Feb 2003 03:58:14 GMT

On Mon, 3 Feb 2003, Erik Price wrote:

> Date: Mon, 03 Feb 2003 17:16:54 -0500
> From: Erik Price <>
> Reply-To: Tomcat Users List <>
> To: Tomcat Users List <>
> Subject: Re: more about custam tag life cycle
> 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?

All generalizations are inherently false, including this one :-).

There are not very many absolutes in programming -- if object pooling
makes your application run faster, by all means use it.  If it doesn't
make your application faster, then don't bother with it.

If you're into the Extreme Programming (XP) approach to iterative
development, you will probably implement things without object pooling
first (because it's simpler), and only migrate to object pooling if (a)
the object creation/GC of this particular kind of object shows up as a
performance hotspot in your analyzer runs, and (b) using an object pool
actually helps.

That being said, you do not really have any choice about whether to design
custom tag classes to support being pooled or not.  The JSP spec requires
you to obey the rules if you want to guarantee portability to all

> Erik


> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message