2013/11/16 Gérald Quintana <[email protected]> > I didn't notice that I sent my question by mail instead of sharing through > Google Groups: >
Whoops, nice catch. I hadn't noticed either. > > > > >> >> *Hi Gérald,The point here is simple. Take ArrayList, for instance. It is > not thread-safe. But if you can ensure that no one will ever modify the > ArrayList after it was initialised, then it is quasi-thread-safe. The same > applies to DefaultDSLContext, which is not thread-safe. But if you > initialise it with Spring and you will never modify it (nor its contents), > then it is also quasi-thread-safe.CheersLukasHi,If the DefaultDSLContext is > not thread safe, is it a good idea to declare it as a bean with singleton > scope as described > in > http://www.jooq.org/doc/3.2/manual/getting-started/tutorials/jooq-with-spring/ > <http://www.jooq.org/doc/3.2/manual/getting-started/tutorials/jooq-with-spring/> > and > then let Spring inject this DSLContext in DAO/Repositories beans?Gérald* > >> >> > I wanted to know whether the DSLContext was wrapping a JDBC Connection. > Obviously it's not the case, it's just wrapping Configuration and a > ConnectionProvider. > Yes, that's correct. ConnectionProvider was introduced in jOOQ 3.0 to allow for better control over the JDBC Connection lifecycle within jOOQ. Cheers, Lukas -- 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/groups/opt_out.
