Hi Romain, I would default to a pool that supports JTA and non-JTA datasources and include its jar. If you plan to support other pools it's reasonable not to include their jars by default, ask people who need other pools to include the jars with their app. Do you plan to make Tomcat pool or BoneCP one the default in Tomee?
Keep in mind DBCP has a nasty issue with abandoned or dropped connection, in production, if DB is restarted, the app server with DBCP has to be restarted as well to be able to reconnect to DB. I know BoneCP does not have this issue because it's part of their tests. This might help you a bit http://www.jorambarrez.be/blog/2012/04/30/dbcp_vs_c3p0_bonecp/ Not sure how Tomcat pool compares. -- View this message in context: http://openejb.979440.n4.nabble.com/default-tomee-ds-pool-tp4656531p4656542.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
