JBossDeveloper

Or if the Object is expensive to construct like a database connection.

Surely MultiThreaded would be worse (more contention)
unless your pooling uses a ThreadLocal pool

I removed all that crap from JBossMQ

I know yours was Bill.

Steve is interested in it in the context of a global pool:
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=48594

What might be nifty is if the container could attempt to pool a resource. If the container finds that one or the other is significantly faster, it could upgrade it to a JCA, or downgrade it to no-pooling.

1. Get 10 objects using pool
2. Create 10 objects w/o pool
3. Compare the times.
4. AOP as needed if the difference is of a significant enough magnitude.

I don't like nifty or cool. It just over complicates things and makes things buggy.

10 is nothing like enought for a test. The JIT doesn't even kick in until you
thousands of repetitions. JITs are bettter at this than you could ever be and
will only get better over time.

Okay. I'm glad the VM is good at that. Like your JCA FAQ says, "Are you *sure* you want JCA?"

Steve

It wouldn't even be testing what I thought it'd be testing. I wonder what the real cutoff points are between

1. The VM developer
2. The Container developer
3. The container user (using JSP, other services on top of the container)

Anyways, I'll be quiet about things now :)