Hello Ian, > I eventually went with BoneCP and it was fairly painless. I was a little > puzzled that all of their examples involve grabbing a connection, and then > closing it. Initially I thought that if you closed the connection it > wouldn't return to the pool, but I then realized that this is probably the > way you indicate that the connection can be returned to the pool.
Yes, with connection pooling, closing a connection has a new semantics, just like "opening" a connection, which doesn't open a new one, but gets one from the pool. In a way, the JDBC Connection's lifecycle is still the same, though. > It's been a while since I've done this kind of J2EE stuff, so much of the > tooling is grossly overengineered, poorly documented, and they all manage to > make the simplest use-cases seriously over-complicated (I'm looking at you > Jersey). jOOQ is a nice exception to that :-) Thank you. You might enjoy these readings about architecture astronauts :-) http://www.joelonsoftware.com/articles/fog0000000018.html http://www.joelonsoftware.com/items/2005/10/21.html http://www.joelonsoftware.com/items/2008/05/01.html Cheers Lukas
