looked a bit more, using tomcat pool you maybe gain some small features but you lost some others and in particular the transaction stuff which would be a pain.
Another JEE6 feature you loose is the @DataSourceDefinition management too i think. So i think i prefer to keep tomcat pools next to tomee pools but not as a replacement. If you could precise which features "afraid" you we could have a look more precisely. - Romain 2012/7/21 Romain Manni-Bucau <[email protected]> > All is not true, was true at a moment. Typically dbcp is ready for prod > and largely used (all spring apps for instance use it too). > > Please find an issue before saying that's not ready. I think we could use > tomcat pool but i didnt tested it (while i know dbcp very well). Feel free > to open a jira, the hack shouldnt be hard. > Le 21 juil. 2012 02:18, "zeeman" <[email protected]> a écrit : > > Why is Tomee still using DBCP? See this >> http://people.apache.org/~fhanik/jdbc-pool/jdbc-pool.html >> >> I don't see why cannot Tomee delegate to Tomcat DB pool. After reading >> limitations of DBCP that I was not aware of I cannot go with it in prod. I >> thought Tomee had a tweaked DB pool like one in jBoss especially for >> concurrency and newer JDKs. >> >> So the next question is that if we Tomee cannot delegate to Tomcat DB >> pool. >> What do I need to do to use Tomcat pool in Tomee? >> >> Is it hard for Tomee to switch to use Tomcat DB pool? >> >> >> >> -- >> View this message in context: >> http://openejb.979440.n4.nabble.com/DB-pool-resource-Tomee-production-tp4656425p4656442.html >> Sent from the OpenEJB User mailing list archive at Nabble.com. >> >
