Hello, Using SMX 4.5, we run into the DriverManager.getDriver problem that has been discussed over the past few years. We inject our own DataSource using c3p0 into Hibernate. Since c3p0 is managing connections, we have created a fragment that exports the jdbc driver into c3p0. This works fine normally. However, after several times of restarting SMX, we find that the fragment is no longer hooked to the c3p0 bundle, and so we get a No Suitable Driver in a stack trace at the point where c3p0 asks the DriverManager to lookup the driver. We clean the cache, and all is well again. We do not wish to clean the cache every start up.
We have read that perhaps karaf 2.3 will change fragment dependency management in a way that will correct this problem. Can anybody confirm this? Is there another idea not based on fragments for using c3p0 in osgi? Or would some client thread pool (bone?) fall back to using TCCL and maybe we could leverage that for a fix? Or if there is no good way to manage our situation, should we just go ahead and add our jdbc driver to the extensions directory? Thanks in advance, Jim -- View this message in context: http://servicemix.396122.n5.nabble.com/fragments-jdbc-driver-manager-bundle-cache-help-tp5716040.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
