Hello, 2014-11-13 4:02 GMT+01:00 Garret Wilson <[email protected]>:
> So our application is almost in production, and we realized that the > proof-of-concept RESTful interface I created (using a jOOQ configuration > wrapping a JDBC connection) had never been changed, so all requests were > using the same connection! I'm now reviewing another teammate's changes and > I wanted to review the jOOQ documentation on this, as this is a little > beyond my expertise. So I looked for the documentation that used to exist > <http://www.jooq.org/doc/2.6/manual/sql-building/factory/connection-vs-datasource/>, > but the version 3.4 manual <http://www.jooq.org/doc/3.4/manual/> doesn't > seem to have anything to say on the subject! > The section has moved here: http://www.jooq.org/doc/latest/manual/sql-building/dsl-context/connection-vs-datasource/ > Where can I read up on how to create a single jOOQ configuration that I > pass around that uses a data source or some other connection factory (that > I can e.g. put a connection pool behind)? Where's the new documentation for > that? Thanks. > Another good page that explains this is the tutorial about using jOOQ with Apache DBCP and Spring: http://www.jooq.org/doc/latest/manual/getting-started/tutorials/jooq-with-spring/ Essentially, you will just need to replace "passing a Connection instance to jOOQ" by "passing a DataSource instance to jOOQ". Whether you want to keep a global jOOQ Configuration, or just a global DataSource creating the jOOQ Configuration afresh at every query usually doesn't really matter. Hope this helps. Let me know if you have any concrete issues. -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
