[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] Incubator request for Extensions/Services Integration work

+1 from me. If needed, I can help with IPZilla.

The area probably could be created with a more general purpose - something like "component models investigation"? equinox-incubator/component-model/service-injection


"Neil Bartlett" <njbartlett@xxxxxxxxx>
Sent by: equinox-dev-bounces@xxxxxxxxxxx

03/27/2008 10:53 AM

Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>

"Equinox development mailing list" <equinox-dev@xxxxxxxxxxx>
[equinox-dev] Incubator request for Extensions/Services Integration        work


I have been doing some investigative work recently in the area of
integrating extensions with OSGi services. As a result of this, I have
developed a small framework for dynamically injecting services into
extension objects according to metadata defined via the extension
registry. As a very simple example, suppose we have an extension
object (e.g. a ViewPart) which has a method
setLogReader(LogReaderService). We can declare an "injected bean"
extension as follows:

   <extension point="...injectedBeans">
       <bean id="logReaderView"
           <injectSingle interface="org.osgi.service.log.LogReaderService"

And then the actual view extension as:

   <extension point="org.eclipse.ui.views">
       <view class="org...InjectedExtensionFactory:logReaderView"
             name="Log Reader"/>

This results in all objects instantiated from the log view extension
being dynamically injected with the log reader service as it becomes
available (and un-injected when it goes away).

I would like to request a work area under the Equinox incubator as a
home for this code so that others can test it and experiment with this
and other approaches to the extensions/services integration problem.

equinox-dev mailing list