[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


equinox-dev-bounces@xxxxxxxxxxx wrote on 03/27/2008 01:08:57 PM:

> +1
>
> I think a "component programming model" incubator area is a great idea.
>
> Tom
>
>
>
> [image removed] "Jeff McAffer" ---03/27/2008 12:06:17 PM---+1

>
> [image removed]
> From:
>
> [image removed]
> "Jeff McAffer" <jeff@xxxxxxxxx>
>
> [image removed]
> To:
>
> [image removed]
> "'Equinox development mailing list'" <equinox-dev@xxxxxxxxxxx>
>
> [image removed]
> Date:
>
> [image removed]
> 03/27/2008 12:06 PM
>
> [image removed]
> Subject:
>
> [image removed]
> RE: [equinox-dev] Incubator request for Extensions/Services Integration
work
>
>
>
>
> +1
>
> This fits well with investigations we need to do for e4 as well as
> the SAT work and some discussions with James Branigan from the Jazz
> team around stuff they have been doing.
>
> Need a pithy name for the workarea. ?component programming model?
> (CPM) perhaps? As Oleg points out, it is really something that is
> broader than just services and extensions.
>
> Jeff
>
> From: equinox-dev-bounces@xxxxxxxxxxx
[mailto:equinox-dev-bounces@xxxxxxxxxxx
> ] On Behalf Of Chris Aniszczyk
> Sent: Thursday, March 27, 2008 11:31 AM
> To: Equinox development mailing list
> Subject: Re: [equinox-dev] Incubator request for Extensions/Services
> Integration work
> +1 also
>
> Cheers,
>
> ---
> Chris Aniszczyk | IBM Lotus | Eclipse Committer | http://mea-bloga.
> blogspot.com | +1.860.839.2465
>
> [image removed] Oleg Besedin ---03/27/2008 10:24:40 AM---+1 from me.
> If needed, I can help with IPZilla. The area probably could be
> created with a more gener
>
>
> From:
>
>
> Oleg Besedin <obesedin@xxxxxxxxxx>
>
>
> To:
>
>
> Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
>
>
> Date:
>
>
> 03/27/2008 10:24 AM
>
>
> Subject:
>
>
> 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
>
> Thanks,
> Oleg

>
> "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>
>
> To
>
> "Equinox development mailing list" <equinox-dev@xxxxxxxxxxx>
>
> cc
>
> [image removed]
>
> Subject
>
> [equinox-dev] Incubator request for Extensions/Services Integration work
>
> [image removed]
>
> [image removed]
>
>
>
>
> Hello,
>
> 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"
> class="org...LogReaderView">
> <injectSingle interface="org.osgi.service.log.LogReaderService"
> set="setLogReader"/>
> </bean>
> </extension>
>
> And then the actual view extension as:
>
> <extension point="org.eclipse.ui.views">
> <view class="org...InjectedExtensionFactory:logReaderView"
> name="Log Reader"/>
> </extension>
>
> 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.
>
> Regards,
> Neil
> _______________________________________________
> equinox-dev mailing list
> equinox-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/equinox-dev
> _______________________________________________
> equinox-dev mailing list
> equinox-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/equinox-dev
> _______________________________________________
> equinox-dev mailing list
> equinox-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/equinox-dev
> _______________________________________________
> equinox-dev mailing list
> equinox-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/equinox-dev