> By the way, JOOQ with a connection pool is really nice. I can pretty much > stick a single JOOQ statement anywhere I like and it does everything for me! > No need to get a connection and make sure it is cleaned up :)
Good to know, thanks for the feedback. Yes, using jOOQ should result in much less boilerplate than using JDBC. After all, all that boring try / catch / finally stuff isn't what we're really paid for Once you understand that you have to use a *pooled* DataSource, things work out quite nicely. It's just a bit confusing to realise what parts of the connection-related API can then still be used. Also, not everyone wants pooled DataSources...
