When should I use Import-Package and when should I use Require-Bundle?

by

I believe Require-Bundle is an Eclipse thing (that has now made it in the OSGi spec to accommodate Eclipse). The “pure” OSGi way is to use Import-Package, as it specifically decouples the package from the bundle that provides it. You should be declaring dependencies on functionality that you need (the Java API provided by a certain version of a certain package) instead of where that functionality is coming from (which should not matter to you). This keeps the composition of bundles more flexible.

JavaScript analogy: This is like detecting whether a web browser supports a certain API versus inferring from what the user-agent string says what kind of browser it is.

Peter Kriens of the OSGi Alliance has more to say about this on the OSGi blog.

Probably the only case where you need to use Require-Bundle is if you have split packages, that is a package that is spread across multiple bundles. Split packages are of course highly discouraged.

More Related Contents:

  1. Reading my own Jar’s Manifest
  2. What does OSGi solve?
  3. Programmatically Start OSGi (Equinox)?
  4. How to use JavaFX Preloader with stand-alone application in Eclipse?
  5. How to convert jar to OSGi bundle using eclipse and bndtools
  6. Convert existing JAR to OSGi-bundle
  7. Java 8 & Missing required capability Require-Capability: osgi.ee; filter=”(&(osgi.ee=JavaSE)(version=1.8))”
  8. How to create OSGi bundle from jar library?

Leave a Comment