Hey,
Once I saw servicemix had its own bundle of the commons-dbcp. I switched it
and the thing started to work like as it should.
Much appreciated for listing out that artifact.
--
View this message in context:
http://camel.465427.n5.nabble.com/C3P0-cannot-load-Jtds-Driver-in-OSGi-env-tp56
, 2012 19:09
To: users@camel.apache.org
Subject: Re: C3P0 cannot load Jtds Driver in OSGi env
glad it worked for you!
Sven's example sounds more elegant and robust for a larger scenario, but
it's pushing the boundaries of my current skill level. i'll revisit once
i've learned mor
glad it worked for you!
Sven's example sounds more elegant and robust for a larger scenario, but
it's pushing the boundaries of my current skill level. i'll revisit once
i've learned more.
~ Reuben
On Thu, Mar 29, 2012 at 12:02, raad wrote:
> Reuben, I chose your method and it worked fine. T
Reuben, I chose your method and it worked fine. Thanks for the response.
But I do like the idea of having a fractional bundle where the dbcp and the
jdbc driver live in the same classpath.
Again thank for responding.
--
View this message in context:
http://camel.465427.n5.nabble.com/C3P0-cann
Thanks Sven. I've seen the issue in several blogs. I appreciate the
response.
--
View this message in context:
http://camel.465427.n5.nabble.com/C3P0-cannot-load-Jtds-Driver-in-OSGi-env-tp5601253p5604416.html
Sent from the Camel - Users mailing list archive at Nabble.com.
We ran into similar issues (DBCP as well). Our solution was to create a bundle
that embedded (Bundle-Classpath) JTDS and DBCP into a single bundle so that
they shared classpath. From there you can export the necessary packages so any
other bundle may create the DataSource/Connection instances
