| OSGi and plugin order [message #191647] |
Mon, 09 February 2004 17:34  |
Eclipse User |
|
|
|
Originally posted by: richkulp.NO.SPAM.us.ibm.com
I used to use IPluginVisitor and PluginRegistry.accept(visitor, boolean)
so that I could process the extensions for an extension point in plugin
dependency order. I must process the extensions such that any extensions
for pre-reqed plugins were processed before the dependent plugin, and
all plugins were visted only once.
I know this was internal, but it is now gone. Is there a new way to do
this. One that is API? I don't know anything about OSGi other than what
was said in the discussion on the Eclipse org site about it.
--
Thanks, Rich Kulp
|
|
|
| Re: OSGi and plugin order [message #192318 is a reply to message #191647] |
Tue, 10 February 2004 22:42  |
| Eclipse User |
|
|
|
Originally posted by: jeff_mcaffer_REMOVE.ca.ibm.com
Rich,
Extensions and extension points are part of the Eclipse runtime (as opposed
to being part of the OSGi framework). There is a new registry
(IExtensionRegistry). Since the extension-extension point relationship is
separate from the plugin dependency relationship, there is no general way to
provide the traversal you want. Put more simply, just because A provides an
extension to some point in B does not mean that A explicitly or implicitly
depends on B.
I'm not sure what you are trying to do but the standard approach we take is
to process the elements in whatever order and remember the orphans and then
hook them up as you discover more.
Sidenote: To be a good citizen in the new dynamic world (if that is
interesting in your scenarios), you should also consider listening for
registry events and updating your structures as things come and go.
Jeff
"Rich Kulp" <richkulp@NO.SPAM.us.ibm.com> wrote in message
news:c091om$f3s$1@eclipse.org...
> I used to use IPluginVisitor and PluginRegistry.accept(visitor, boolean)
>
> so that I could process the extensions for an extension point in plugin
> dependency order. I must process the extensions such that any extensions
> for pre-reqed plugins were processed before the dependent plugin, and
> all plugins were visted only once.
>
> I know this was internal, but it is now gone. Is there a new way to do
> this. One that is API? I don't know anything about OSGi other than what
> was said in the discussion on the Eclipse org site about it.
>
> --
> Thanks, Rich Kulp
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.05013 seconds
Home