> > > In other projects, I had a ConnectionProvider for this which either > wrapped > > a normal sql.Connection or a DataSource (where it would request and > return > > the connection) or something else. > > The best thing for this provider would be to implement DataSource and > be supplied as such to a jOOQ Factory >
I'd like to avoid this because of the unstable JDBC API: With every release, Sun adds some new methods which breaks code that extends JDBC interfaces :-( So a new interface which just has two methods (borrowConnection() and returnConnection()) would move the unstable part into jOOQ hiding it from all your consumers. Regards, A. Digulla
