I would advise against using the imports. That will tie your bundle directly to the database vendor. If you use jndi then you have a layer of abstraction. On Aug 14, 2012 7:16 AM, "Julien Martin" <[email protected]> wrote:
> Thanks James, > Your advice is interesting. I am definitely going to test this feature. > However, what I'd really like to do now is understand how to configure the > package Imports/Exports. > Regards, > J. > > 2012/8/14 James Carman <[email protected]> > >> You might try defining your data source in a simple XML file (either >> Spring or preferably blueprint) in your deploy directory. Then, you >> don't have to worry about the imports. Karaf will automatically set >> up dynamic importing for you on any module deployed this way. Then, >> you just refer to your data source via JNDI (don't forget to install >> the jndi feature). >> >> On Tue, Aug 14, 2012 at 4:33 AM, Julien Martin <[email protected]> wrote: >> > Hi Ioannis, >> > What is the exact package are you referring to? >> > What about the odd behavior I noticed and was mentioning above? >> > Regards, >> > Julien. >> > >> > >> > >> > 2012/8/14 Ioannis Canellos <[email protected]> >> >> >> >> Bitronix uses the Thread Context Class Loader in order to load the >> driver >> >> class, so there is no need for you to configure bitronix or >> spring-batch to >> >> directly import that package. >> >> >> >> Instead you should make sure that these mysql packages are imported by >> the >> >> bundle that contains the spring context and I think that it should >> just work >> >> (I am not 100% sure that spring set the TCCL to the current bundle, >> but I >> >> think that springdm does that by default). >> >> >> >> -- >> >> Ioannis Canellos >> >> FuseSource >> >> >> >> Blog: http://iocanel.blogspot.com >> >> Twitter: iocanel >> >> >> >> >> > >> > >
