Question

I am interested in using OSGI as a means of managing plugins for a project. That is there can be many implemenators of my interface, each appearing in its own / separate OSGI bundle with the implementation class exported…

Answer 1

Declarative Service should be the way to go.

You can declare your interface as a service

<service>     <provide interface='my.Interface'/>     <property name='foo' value='bar' </service> 

Each implementation of that interface can define Bundle activation and de-activation methods.
But what is really neat is their nature: if you are using the latest SCR (the ‘Service Component Runtime’ which is an ‘extender bundle’ implementing the new and improved OSGi R4.2 DS – Declarative Service – specification), your classes will not import anything from the OSGI model. They remain pure POJO.

Then define another service which depends on your first service:

<reference name='myInterfaceServiceName'     interface='my.Interface'     bind='myActivationMethod' unbind='myDeactivationMethod'     cardinality='0..n'/> 

That service will detect and list all your concrete instances of your first service and deal with them as you intent to.

See the Eclipse Extensions and Declarative Services question for more details.

The presentation: Component Oriented Development in OSGi with Declarative Services, Spring Dynamic Modules and Apache iPOJO, from EclipseCON2009, will provide you with a concrete example.