RE: [jbosscache-dev] Using Apache DBCP in NonManagedConnectionFactory

The name of the class says it all "NonManagedConnectionFactory". It's meant to be managed by a transaction. If the user is looking to manage the connection himself either with a custom connection pooling or otherwise, he/she should be looking at using ManagedConnectionFactory and vendor specific implementation of that. I know that Oracle, Derby and perhapes the rest of the DB vendors provide implementation for managed connection factories to handle concurrency situations such as this one. -Hany Hany M. Mesha Sr. Software Engineer, Consultant Novell Identity Management Engineering Toronto, Canada hmesha(a)novell.com Mobile: 416-456-6945 skype: hanymesha Novell, Inc. SUSE® Linux Enterprise 10 Your Linux is ready http://www.novell.com/linux Never underestimate people's stupidity, like me for example. On a more serious note, can this pooling be isolated and then use interchangable pooling implementations? How does hibernate make it interchangable? They must be using some adaptation layer? My main point is to see what they have done and not reinvent the wheel. _______________________________________________ jbosscache- dev mailing list jbosscache- dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosscache- dev