Home/ Questions/Q 8738557
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-13T10:45:26+00:00

I’m working on a project, it’s integration project, we are using Apache Camel and

  • 0

I’m working on a project, it’s integration project, we are using Apache Camel and Apache Karaf.
In the project, I need to use the Jira REST Java client library.

So I’ve read quite a lot of various articles and threads about how to wrap non-OSGI library to OSGI bundle, but I’m really not sure if I got it right.

So, I’ve created a POM file with a dependency to the needed library. Made a package and tried to deploy it to Karaf, of course, Karaf complained for missing packages.

So, I’ve found corresponding maven dependency, added it, package goes into <Import-Package> and dependency into <Embed-Dependency>.

Another round, deploy, find dependency, add, … and again, and again, until Karaf is fine with the bundle.

Is that really correct? It seems to me like quite crazy, so I guess I don’t got it as usualy 🙂

Finally, the package get to stable that was on my work computer, I checked it quickly and went home, there I continued but, strange, the same POM / package, compiled on my personal computer is not working, again complaining about missing package, but this time, this package is for sure in the POM file and for sure it is embeded in the package, I can see it there.

This missing package is this time org.apache.commons.codec.

org.osgi.framework.BundleException: Unresolved constraint in bundle jiraclient.bundle [134]: Unable to     resolve 134.0: missing requirement [134.0] osgi.wiring.package; (osgi.wiring.package=org.apache.commons.codec)
    at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:3826)[org.apache.felix.framework-4.0.3.jar:]
    at org.apache.felix.framework.Felix.startBundle(Felix.java:1868)[org.apache.felix.framework-4.0.3.jar:]
    at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:944)[org.apache.felix.framework-4.0.3.jar:]
    at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundle(DirectoryWatcher.java:1247)[6:org.apache.felix.fileinstall:3.2.6]
    at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundles(DirectoryWatcher.java:1219)[6:org.apache.felix.fileinstall:3.2.6]
    at org.apache.felix.fileinstall.internal.DirectoryWatcher.startAllBundles(DirectoryWatcher.java:1208)[6:org.apache.felix.fileinstall:3.2.6]
    at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:503)[6:org.apache.felix.fileinstall:3.2.6]
    at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:291)[6:org.apache.felix.fileinstall:3.2.6]

So, now I’m totally confused, what is wrong 🙁

Pretty please, guys, help me. Thanks!

The POM file is long, so I guess link is better: http://pastebin.com/j5cmWveG

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Yes OSGi is IMHO “far from easy to use” in terms of its deployment model, requiring 100% bundles with osgi metadata in MANIFEST.MF files. And you need a PhD in mathematics to understand the BND tool. And unfortunately many JARs are not OSGi bundles.

    Looking at your pom.xml file with all the imports|exports, and that “not easy to understand” syntax, would just take 5-sec for any average engineer to understand that this “something is wrotten in the state of Denmark” ; eg OSGi != the world we live in. This must and should be easier IMHO.

    You can install a plain JAR in Karaf using the wrap url handler:
    http://karaf.apache.org/manual/latest/developers-guide/creating-bundles.html

    Another trick is to create an uber JAR, eg to put it all in a single JAR file and then you can deploy that.

    There is also FAB (Fuse Bundles) which makes OSGi deployment easier, as it handles much of this craziness for you at deploy time, instead of you having to deal with the OSGi MANIFEST.MF madness: http://www.davsclaus.com/2012/08/osgi-deployment-made-easy-with-fab.html

    • 0