|
|
|
| Re: extension points vs osgi services [message #106739 is a reply to message #106712] |
Thu, 20 March 2008 20:36   |
Eclipse User |
|
|
|
Originally posted by: fireresq.embarqmail.com
thanks I went to the panel ant it was very interesting. Looking forward to reading the other papers and getting involved with
the OSGi project.
John E. Conlon wrote:
> Hi Mark,
>
> What a timely question!
>
> In addition to Neil's fine article, you should know this is a hot panel
> topic
> http://www.eclipsecon.org/2008/index.php?page=sub/&id=49 2
>
> that is being discussed today at the OSGi DevCon
> http://www.osgi.org/Conference/HomePage
> (which is part of EclipseCon)
>
> See Perter Kriens' OSGi blog, I am sure he will blog about it
> today/tomorrow:
> http://www.osgi.org/blog/
>
> IMHO - use both. If you have services that are external and dynamic use
> the OSGi services (ServiceTracker usage is the simplest) for
> Workbench/Eclipse RCP interface extensions use the Extensions.
>
> cheers,
> John
>
> Danail Nachev wrote:
>> Hi,
>>
>> Here is a good comparison between Extension Registry and OSGi Service
>> Registry written by Neil Barlett:
>>
>> http://neilbartlett.name/downloads/extensions_vs_services.pd f
>>
>> Danail
>>
>> Mark Russell wrote:
>>> how should I decide which to use? Could some one point to good articles
>>> to help me make the decision
|
|
|
|
| Re: extension points vs osgi services [message #106841 is a reply to message #106641] |
Wed, 26 March 2008 11:24 |
| Eclipse User |
|
|
|
Originally posted by: Boyan.Yurukov.softwareag.com
Here is a short explanation as I get it. I am not sure if it would come out
accurate:
OSGi services are basic java objects that are put in a registry for other
bundles to use. Usually one exports an interface they implement so that the
other bundles can easily use them. When bundle A requires bundle B and it
expects a service from it, most often A knows of what interface the service
is and the service call is hardwired. So overall one has a java object that
recieves calls from other bundles.
An extention point, on the other hand is a definition of a "requirement" for
extention. There is no passed functionality, but a "request" for
functionality, which, when provided through an extenstion, is then handled
inside the bundle. In my view an OSGI service is closer to an extenstion in
the sence that a bundle publishes code for the others to use. However, in an
extention we provide that functionality for a specific bundle and we don't
pass an object, but just a class name and some text properties. That class
name is later used in the bundle, that specified the extention point, to
create an instance and use the new functionality.
Hope I didn't sound too messed up.
Greetings,
Boyan.
"Mark Russell" <fireresq@embarqmail.com> wrote in message
news:frsmnm$gjs$1@build.eclipse.org...
> how should I decide which to use? Could some one point to good articles to
> help me make the decision
|
|
|
Powered by
FUDForum. Page generated in 0.03801 seconds
] 
Search
Help
Register
Login
Home
