db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kristian Waagan <Kristian.Waa...@Sun.COM>
Subject Re: ClientDataSource in OSGi
Date Wed, 25 Mar 2009 20:35:16 GMT
JJ Snyder wrote:
> After further investigation it appears the the derbyclient.jar is not 
> a complete bundle.  The manifest is terse and does not export 
> anything.  I grabbed the spring source version of the derby bundles 
> and their derbyclient manifest is quite detailed including the correct 
> export package.  I am able to use it without issue.

Good to hear that you have been able to work around the issue.
I don't know OSGi very well. Would you say that the Derby bundle is 
broken, and needs to be fixed? Or does it require some extra 
configuration to work?

If you think this is a Derby bug, feel free to log a Jira issue at 

Thank you for your feedback!

> JJ
> Kristian Waagan wrote:
>> JJ Snyder wrote:
>>> Hi,
>>> I am running Equinox standalone and have installed and started the 
>>> derby bundle (derby.jar). I am able to access the EmbeddedDataSource 
>>> from another bundle successfully.  I then install and start the 
>>> derbyclient.jar as a bundle but when I try to access the 
>>> ClientDataSource I get a ClassNotFoundException.  It works fine in 
>>> eclipse' PDE environment but not standalone.
>>> Any ideas?
>> Hello,
>> I don't have much to offer now, but can you please post the stack trace?
>> Is it the ClientDataSource class that isn't found, or a different class?
>> Regards,

View raw message