Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Equinox » Is this official API - IExtensionRegistry#addListener(IRegistryEventListener)?
Is this official API - IExtensionRegistry#addListener(IRegistryEventListener)? [message #105977] Fri, 07 March 2008 22:23 Go to next message
Eclipse UserFriend
Originally posted by: mark_melvin.amis.com

Hello All,

I am currently using the newer
IExtensionRegistry#addListener(IRegistryEventListener) family of methods,
and I plan to mention them in my EclipseCON talk on extension points.
However, there is a comment in the Javadoc (I am running on 3.4M5) that
says:

* <b>Note:</b> This is a preliminary form of a new API that might change
or be removed
* altogether prior to 3.4 release. It is being made available at this
early stage to solicit
* feedback from early adopters.

Do you plan on keeping this as official API? If so I will encourage its
use. Otherwise perhaps I should not mention it?

Thanks,
Mark.
Re: Is this official API - IExtensionRegistry#addListener(IRegistryEventListener)? [message #106097 is a reply to message #105977] Tue, 11 March 2008 02:39 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: mark_melvin.amis.com

Anyone?

M.


On Fri, 07 Mar 2008 17:23:43 -0500, Mark Melvin <mark_melvin@amis.com>
wrote:

> Hello All,
>
> I am currently using the newer
> IExtensionRegistry#addListener(IRegistryEventListener) family of
> methods, and I plan to mention them in my EclipseCON talk on extension
> points. However, there is a comment in the Javadoc (I am running on
> 3.4M5) that says:
>
> * <b>Note:</b> This is a preliminary form of a new API that might
> change or be removed
> * altogether prior to 3.4 release. It is being made available at this
> early stage to solicit
> * feedback from early adopters.
>
> Do you plan on keeping this as official API? If so I will encourage its
> use. Otherwise perhaps I should not mention it?
>
> Thanks,
> Mark.
Using ExtensionTracker [was Re: Is this official API - IExtensionRegistry#addListener(IRegistryEvent [message #106166 is a reply to message #106097] Tue, 11 March 2008 16:15 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: mark_melvin.amis.com

OK, I have done some more digging and found that this API is only slightly
used compared to tracking extensions using
org.eclipse.core.runtime.dynamichelpers.ExtensionTracker. I think I am
just going to port my example to use ExtensionTracker instead of listening
to the extension registry directly.

Does anyone have any recommendations one way or the other?

Mark.

On Mon, 10 Mar 2008 22:39:56 -0400, Mark Melvin <mark_melvin@amis.com>
wrote:

> Anyone?
>
> M.
>
>
> On Fri, 07 Mar 2008 17:23:43 -0500, Mark Melvin <mark_melvin@amis.com>
> wrote:
>
>> Hello All,
>>
>> I am currently using the newer
>> IExtensionRegistry#addListener(IRegistryEventListener) family of
>> methods, and I plan to mention them in my EclipseCON talk on extension
>> points. However, there is a comment in the Javadoc (I am running on
>> 3.4M5) that says:
>>
>> * <b>Note:</b> This is a preliminary form of a new API that might
>> change or be removed
>> * altogether prior to 3.4 release. It is being made available at this
>> early stage to solicit
>> * feedback from early adopters.
>>
>> Do you plan on keeping this as official API? If so I will encourage
>> its use. Otherwise perhaps I should not mention it?
>>
>> Thanks,
>> Mark.
Re: Using ExtensionTracker [was Re: Is this official API - IExtensionRegistry#addListener(IRegistryE [message #106250 is a reply to message #106166] Wed, 12 March 2008 19:47 Go to previous messageGo to next message
Oleg Besedin is currently offline Oleg BesedinFriend
Messages: 41
Registered: July 2009
Member
Hi Mark,
Yes, this is the "official" :-) API. That is the usual disclaimer in case a
new API needs to be changed between an introduction and an API freeze. In
fact, it is time to remove it, thanks for the reminder.

In terms of what to use - it depends on what's more convenient for you.
Generally speaking, the new listener was added to help with the same
scenario as the ExtensionTracker class: keeping a local cache in sync with
the registry. The new listener should result in a simpler code for new
implementations, but if you have code that uses ExtensionTracker and
comfortable with it, there is really no need to switch.

Hope this helps.

Thanks you,
Oleg Besedin


"Mark Melvin" <mark_melvin@amis.com> wrote in message
news:op.t7u0r0dpy7f1g1@n-mmelvin.pc.amis.com...
> OK, I have done some more digging and found that this API is only slightly
> used compared to tracking extensions using
> org.eclipse.core.runtime.dynamichelpers.ExtensionTracker. I think I am
> just going to port my example to use ExtensionTracker instead of listening
> to the extension registry directly.
>
> Does anyone have any recommendations one way or the other?
>
> Mark.
>
> On Mon, 10 Mar 2008 22:39:56 -0400, Mark Melvin <mark_melvin@amis.com>
> wrote:
>
>> Anyone?
>>
>> M.
>>
>>
>> On Fri, 07 Mar 2008 17:23:43 -0500, Mark Melvin <mark_melvin@amis.com>
>> wrote:
>>
>>> Hello All,
>>>
>>> I am currently using the newer
>>> IExtensionRegistry#addListener(IRegistryEventListener) family of
>>> methods, and I plan to mention them in my EclipseCON talk on extension
>>> points. However, there is a comment in the Javadoc (I am running on
>>> 3.4M5) that says:
>>>
>>> * <b>Note:</b> This is a preliminary form of a new API that might
>>> change or be removed
>>> * altogether prior to 3.4 release. It is being made available at this
>>> early stage to solicit
>>> * feedback from early adopters.
>>>
>>> Do you plan on keeping this as official API? If so I will encourage
>>> its use. Otherwise perhaps I should not mention it?
>>>
>>> Thanks,
>>> Mark.
Re: Using ExtensionTracker [was Re: Is this official API - IExtensionRegistry#addListener(IRegistryE [message #106320 is a reply to message #106250] Thu, 13 March 2008 16:00 Go to previous message
Eclipse UserFriend
Originally posted by: mark_melvin.amis.com

Hi Oleg,

Thank you very much for the reply! It's good to know. :-)

Mark.


On Wed, 12 Mar 2008 15:47:21 -0400, Oleg Besedin <obesedin@ca.ibm.com>
wrote:

> Hi Mark,
> Yes, this is the "official" :-) API. That is the usual disclaimer in
> case a
> new API needs to be changed between an introduction and an API freeze. In
> fact, it is time to remove it, thanks for the reminder.
>
> In terms of what to use - it depends on what's more convenient for you.
> Generally speaking, the new listener was added to help with the same
> scenario as the ExtensionTracker class: keeping a local cache in sync
> with
> the registry. The new listener should result in a simpler code for new
> implementations, but if you have code that uses ExtensionTracker and
> comfortable with it, there is really no need to switch.
>
> Hope this helps.
>
> Thanks you,
> Oleg Besedin
>
>
> "Mark Melvin" <mark_melvin@amis.com> wrote in message
> news:op.t7u0r0dpy7f1g1@n-mmelvin.pc.amis.com...
>> OK, I have done some more digging and found that this API is only
>> slightly
>> used compared to tracking extensions using
>> org.eclipse.core.runtime.dynamichelpers.ExtensionTracker. I think I am
>> just going to port my example to use ExtensionTracker instead of
>> listening
>> to the extension registry directly.
>>
>> Does anyone have any recommendations one way or the other?
>>
>> Mark.
>>
>> On Mon, 10 Mar 2008 22:39:56 -0400, Mark Melvin <mark_melvin@amis.com>
>> wrote:
>>
>>> Anyone?
>>>
>>> M.
>>>
>>>
>>> On Fri, 07 Mar 2008 17:23:43 -0500, Mark Melvin <mark_melvin@amis.com>
>>> wrote:
>>>
>>>> Hello All,
>>>>
>>>> I am currently using the newer
>>>> IExtensionRegistry#addListener(IRegistryEventListener) family of
>>>> methods, and I plan to mention them in my EclipseCON talk on extension
>>>> points. However, there is a comment in the Javadoc (I am running on
>>>> 3.4M5) that says:
>>>>
>>>> * <b>Note:</b> This is a preliminary form of a new API that might
>>>> change or be removed
>>>> * altogether prior to 3.4 release. It is being made available at this
>>>> early stage to solicit
>>>> * feedback from early adopters.
>>>>
>>>> Do you plan on keeping this as official API? If so I will encourage
>>>> its use. Otherwise perhaps I should not mention it?
>>>>
>>>> Thanks,
>>>> Mark.
>
Previous Topic:get bundleInfo/bundleContext for classes within a bundle outside activator
Next Topic:log4j Unexpected Result
Goto Forum:
  


Current Time: Fri Oct 22 01:34:42 GMT 2021

Powered by FUDForum. Page generated in 0.01837 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top