Poking Dain, hoping he can give some feedback. Dain was the one who added the JTA support to DBCP when we needed it. It was a pretty decent undertaking then. I.e. didn't fit terribly well.
Redoing that in the Tomcat connection pooling might be possible. Anything that uses the java.util.concurrent libraries is likely way better. -David On Jul 21, 2012, at 11:57 AM, Romain Manni-Bucau wrote: > FYI using dbcp JTA part with a tomcat-jdbc backend pool is a bad idea we > loose a lot of benefit of tomcat-jdbc and code is not clean. > > next idea is to either find a way to contribute to commons-dbcp tomcat > features or to let our DataSourceFactory create simple datasources and > manage ourself JTA link (= all manageddatasoruce stuff of commons dbcp from > our own code with proxies) > > wdyt? > > - Romain > > > 2012/7/21 Romain Manni-Bucau <rmannibu...@gmail.com> > >> Do we try to use tomcat dbcp in tomee? It misses jta features. >>
