That's good stuff, Chuck - and sadly, so prevalent among many places as the
thought process.
-Original Message-
From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com]
Sent: Wednesday, November 11, 2009 2:34 PM
To: Tomcat Users List
Subject: RE: [OT] ConnectionPool que
rale, Charles R <
chuck.caldar...@unisys.com> wrote:
> > From: Josh Gooding [mailto:josh.good...@gmail.com]
> > Subject: Re: [OT] ConnectionPool question
> >
> > Not only did I get yelled at for having the audacity to write up
> > procedures for the developers on my tea
> From: Josh Gooding [mailto:josh.good...@gmail.com]
> Subject: Re: [OT] ConnectionPool question
>
> Not only did I get yelled at for having the audacity to write up
> procedures for the developers on my team
"But we've always done it that way..."
"A long
Chris,
I AM going to use Elli's suggestion. It's going to take some time, but I
don't have to worry, once it's done, it'll be done correctly.
Not only did I get yelled at for having the audacity to write up procedures
for the developers on my team (assuming I ever get a another team), but I
told
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Josh,
On 11/10/2009 9:18 AM, Josh Gooding wrote:
> the reason there are multiple recycleConnection methods is because if a RS
> is passed to the front presentation layer, I have to have a way to close it,
> I have to be able to get the statement and c
I'm glad I amuse all of you :P
Chris,
the reason there are multiple recycleConnection methods is because if a RS
is passed to the front presentation layer, I have to have a way to close it,
I have to be able to get the statement and connection somehow, and I don't
want that in my code.
>From
Chris, as long as we are having fun its all good. I think this
question is something many developers ask. I have seen it here and in
other forums.
You are correct, everything is wrapped. The connection wrapper spawns
statment wrappers which spawn result set wrappers, and everything is
tracked in p
