|
|
Re: Eclipse & Datanucleus - OSGI problem? [message #632186 is a reply to message #632080] |
Tue, 12 October 2010 00:43 |
Marco Lopes Messages: 61 Registered: September 2010 |
Member |
|
|
Response from BoneCP:
This is what bonecp exports:
Export-Package: com.jolbox.bonecp;uses:="com.google.common.base,com.jo
lbox.bonecp.proxy,javax.management,org.slf4j,javax.sql,com.j olbox.bon
ecp.hooks,jsr166y,javax.xml.parsers,org.w3c.dom,javax.naming ,javax.na
ming.spi,com.google.common.collect",com.jolbox.bonecp.hooks;uses:= "co
m.jolbox.bonecp,org.slf4j",com.jolbox.bonecp.proxy,jsr166y;uses:= "sun
.misc"
Response from DataNucleus:
As has been said before (more than once), any jar you put in an OSGI env has to have that manifest, and you haven't put an OSGi-ified BoneCP/C3P0/DBCP jar in the OSGi container - you've used the "normal" jar. So when a DN OSGi bundle tries to find the import that it requires it can't find it ... since you haven't provided it. So do as that person said and check the manifests of the jars you're using. The DN jars all have the right ImportPackage lines.
Spring provide bundles of many software products with such manifests included, or you repackage the bonecp/c3p0/dbcp jar(s) putting manifests in with the right ExportPackage statements as told.
:-\
[Updated on: Tue, 12 October 2010 00:44] Report message to a moderator
|
|
|
Powered by
FUDForum. Page generated in 0.03167 seconds