JDBC driver resolution with pool
I wonder which mechanisms Spring DM Server uses in order to make pools find JDBC drivers. With standard OSGi applications, we use to develop a fragment bundle in order to extend the Import-Package header in the bundle of the pool.
Is there an automatic discovery or something to configure? I made some tests with dbcp and c3p0. With only importing the bundle of the driver in the datasource bundle, it works with the first pool but with the second...
Thanks for your help!