OSGI Bundle and Imports

[guest]

I've developed a few OSGI bundles that I launch with a specific feature.  One of the bundles is 'API'-oriented code that at runtime, basically reads a property file to find out which classes to load.  i.e.

(Prop file):

class=com.mycom.SampleClass

(Code in bundle):

Class.forName... //Does all the reflection based stuff to construct

One of my other bundles define com.mycom.SampleClass.  But in order for my feature to run i have to put

<Import-Package>com.mycom</Import-Package>

in the 'API' bundle's pom.xml in order for it to run.  I feel like this makes my 'API' bundle have to be aware of package names of dynamically loaded classes at compile time.... Is there a better way to do this?  Thanks!

[davsclaus]

There is a dynamic import you can put in the MANIFEST.MF file.

For example see this blog:

http://blog-o-lok.blogspot.com/2008/01/osgi-and-dynamicimport-package.html

[ffang]

Hi,

I believe what you mentioned is the SPI mechanism for JAVA API, as it's a general problem across lots of APIs, in smx4 we use OsgiLocator to resolve this issue. The OsgiLocator is in , the api bundle which use it for example is .

Also, as Claus pointed, you can simply add dynamic-import into your api bundle to resolve it in most case.

https://svn.apache.org/repos/asf/servicemix/smx4/specs/trunk/locator/

https://svn.apache.org/repos/asf/servicemix/smx4/specs/trunk/jaxws-api-2.1/

Freeman