Hi,
the problem is not around the JDBC driver itself (it's very easy to wrap
it as a bundle, or use the wrap protocol).
The problem is more the way the you load (you or a JPA framework such
Hibernate) the driver.
For instance, Class.forName() depends from which classloader, Thread
context class loader is most of the time a better approach in OSGi.
Regards
JB
On 02/17/2012 01:58 PM, vs.souza wrote:
Hello fellows.
I am adding MySQL support to my camel routes in servicemix (to work with
JPA) and found this tutorial to generate a bundle from mysql connector
driver:
http://wiki.eclipse.org/Create_and_Export_MySQL_JDBC_driver_bundle
Do you think that is a good practice to add the MySQL connector as a bundle
and do you see any problems that I may face following this approach?
Cheers.
--
View this message in context:
http://servicemix.396122.n5.nabble.com/MySQL-OSGi-Bundle-tp5492390p5492390.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
