| Running within the classloader context of a different plugin [message #78485] |
Thu, 19 June 2003 12:32  |
Eclipse User |
|
|
|
Originally posted by: myles_jeffery.hotmail.com
Hi,
I have the situation where plugin A provides some core utility classes and
where plugin B makes use of these core utility classes. However, I want
plugin A to call functions on classes within plugin B but plugin A will not
have a dependency on plugin B.
I know that Eclipse uses this pattern a lot, such as a client plugin
registering a view with the Workbench UI plugin which the Workbench then
calls function on.
What is the standard procedure for performing this? Does
Thread.setContextClassLoader () have something to do with it or is there
another method?
Thanks,
Myles
|
|
|
| Re: Running within the classloader context of a different plugin [message #78600 is a reply to message #78485] |
Thu, 19 June 2003 14:34  |
| Eclipse User |
|
|
|
Originally posted by: myles_jeffery.hotmail.com
On further investigation I think I have cracked this one.
PluginDescriptor.createExecutableExtension is what I needed!!!
"Myles Jeffery" <myles_jeffery@hotmail.com> wrote in message
news:bcsoo9$4mv$1@rogue.oti.com...
> Hi,
>
> I have the situation where plugin A provides some core utility classes and
> where plugin B makes use of these core utility classes. However, I want
> plugin A to call functions on classes within plugin B but plugin A will
not
> have a dependency on plugin B.
>
> I know that Eclipse uses this pattern a lot, such as a client plugin
> registering a view with the Workbench UI plugin which the Workbench then
> calls function on.
>
> What is the standard procedure for performing this? Does
> Thread.setContextClassLoader () have something to do with it or is there
> another method?
>
> Thanks,
>
> Myles
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.06054 seconds
Home