I'm confused on how DataSourceConnectionProvider is supposed to be used.  
DataSourceConnectionProvider holds a reference to last connection that was 
acquired.  So the object is not thread safe.  In what context would you use 
DataSourceConnectionProvider?  The only thing I can think of is that when 
using Spring TransactionAwareDataSourceProxy you won't notice the 
non-thread safety because TransactionAwareDataSourceProxy essentially grabs 
a thread local connection.  Is it possible that 
DataSourceConnectionProvider is really spring specific?  If so, should it 
be renamed?

Darren

-- 
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.

Reply via email to