RE: Releasing Resources

[Robin Walker <gnujsp@mail.robin.net>]

Thanks, everybody.  What I'm going to do for now is grab the connections I
need at request time, run my queries, and then give them right back to the
pool as the request-time processing ends - as some of you suggested.  That
seems pretty easy and that way I can just get this thing working.

Once I've done that I may try implementing HttpSessionBindingListener for
fun. I like the idea of just getting your connection once for a user and 
then giving it back once when they're sesion is over, and not writing a
few lines of code to get/return connections inside every single method
that involves queries - but I only like it from a coding standpoint :-) It
may not be as practical in production because you could often be tying up
connections unnecessarily in that you are waiting for sessions to time out
before giving them back. It was suggested that there may be no reason for
a user to have the same connection across requests, and in my case that's
certainly true.

Thanks for the heads up on finalize()

-Robin