| RE: [equinox-dev] Incubator request for Extensions/Services Integration work |
+1
John
Arthorne/Ottawa/I
BM@IBMCA To
Sent by: Equinox development mailing list
equinox-dev-bounc <equinox-dev@xxxxxxxxxxx>
es@xxxxxxxxxxx cc
Subject
03/27/2008 03:03 RE: [equinox-dev] Incubator
PM request for
Extensions/Services
Integration work
Please respond to
Equinox
development
mailing list
<equinox-dev@ecli
pse.org>
+1
Thomas Watson
<tjwatson@xxxxxxxxxx>
Sent by: To
equinox-dev-bounces@eclipse Equinox development mailing list
.org <equinox-dev@xxxxxxxxxxx>
cc
03/27/2008 01:08 PM Subject
RE: [equinox-dev] Incubator
request for
Please respond to Extensions/Services Integration
Equinox development work
mailing list
<equinox-dev@xxxxxxxxxxx>
+1
I think a "component programming model" incubator area is a great idea.
Tom
(Embedded image moved to file: pic08750.gif)Inactive hide details for "Jeff
McAffer" ---03/27/2008 12:06:17 PM---+1"Jeff McAffer" ---03/27/2008
12:06:17 PM---+1
(Embedde (Embedded image moved to file: pic18337.gif)
d image "Jeff McAffer" <jeff@xxxxxxxxx>
moved to
file:
pic25723
.gif)
From:
(Embedde (Embedded image moved to file: pic23642.gif)
d image "'Equinox development mailing list'" <equinox-dev@xxxxxxxxxxx>
moved to
file:
pic20153
.gif)
To:
(Embedde (Embedded image moved to file: pic15954.gif)
d image 03/27/2008 12:06 PM
moved to
file:
pic31781
.gif)
Date:
(Embedde (Embedded image moved to file: pic29476.gif)
d image RE: [equinox-dev] Incubator request for Extensions/Services
moved to Integration work
file:
pic05779
.gif)
Subject:
+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
(Embedded image moved to file: pic26550.gif)Inactive hide details for Oleg
Besedin ---03/27/2008 10:24:40 AM---+1 from me. If needed, I can help with
IPZilla. The area proOleg 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 To
"Equinox development mailing list"
<equinox-dev@xxxxxxxxxxx>
03/27/2008 10:53 AM cc
(Embedded image moved to file:
pic17105.gif)
Subject
[equinox-dev] Incubator request
for Extensions/Services
Please respond to Integration work
Equinox development mailing
list <equinox-dev@xxxxxxxxxxx>
(Embedded image moved to file:
pic04080.gif)
(Embedd
ed
image
moved
to
file:
pic0461
1.gif)
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
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev
Attachment:
pic08750.gif
Description: GIF image
Attachment:
pic25723.gif
Description: GIF image
Attachment:
pic18337.gif
Description: GIF image
Attachment:
pic20153.gif
Description: GIF image
Attachment:
pic23642.gif
Description: GIF image
Attachment:
pic31781.gif
Description: GIF image
Attachment:
pic15954.gif
Description: GIF image
Attachment:
pic05779.gif
Description: GIF image
Attachment:
pic29476.gif
Description: GIF image
Attachment:
pic26550.gif
Description: GIF image
Attachment:
pic17105.gif
Description: GIF image
Attachment:
pic04080.gif
Description: GIF image
Attachment:
pic04611.gif
Description: GIF image
