This error means you are missing a bundle which export com.technicacorp.util.distributor package.
Thank you for your suggestion. So I should add an export package header to the external jar's manifest file?
I tried to "osgi" an external jar using a tool called bnd. It worked and added export package headers, but when I rebuilt and deployed, I still got the same run time error
I cleaned up the MANIFEST file a little bit for readability:
Created-By: 1.5.0_22 (Sun Microsystems Inc.)
Originally-Created-By: 1.5.0_17-b04 (Sun Microsystems Inc.)
I feel like I am missing something important. Any help is greatly appreciated.
You need install technica -util.jar as a bundle which export com.technicacorp.util.distributor package.
I resolved my issue by issuing the command "osgi:install technica-util.jar" within felix. I then started the bundle with the command "osgi:start 'number of the bundle to start'" and I no longer get my run-time error.
Thank you for your help.
Edited by: rkozura on Aug 3, 2010 3:40 PM
I am sorry to bump this thread, but is there any other way I could have solved this? After trying to develop other web services, I keep getting back to the unresolved constraint issue and it seems sloppy to keep manually adding jar files.
I exported the correct class "com.technicacorp.util.distributor" in the manifest of the jar (that is in the Maven repository), and I imported the package and have the jar as a dependency in the pom.
Anyone have any hints? I would greatly appreciate it.
You need to install the third party jar in the karaf,
Use this command if it works for you,
osgi:install -s wrap:file:///C:/Bridge/wlfullclient.jar
Then include the package name in the Import-Package
Thank you divakar, but this is the way I am doing it now. Is there any possible way to not manually install the jar into osgi?
For instance, can't I just put the jar inside of the local repository and configure the pom to install the jar automatically?
I know I am knit picking, but I am trying to be consistent.
I came across a help saying that, you can install the jar in the local maven repository and include the dependencies in the pom.xml.
BTW I am not an expert in here, I am also try to get some help!
You can put all necessary bundles in features file to do provisioning.
Basically a feature is a set of bundles which can do certain functionality.