| access objects among plugins [message #200854] |
Wed, 21 March 2007 14:41  |
Eclipse User |
|
|
|
Originally posted by: niki.email.ru
Given 2 plugins A and B, I want to access a data member, or call a method
of class reziding in plugin A from plugin B.
Is it possible to do this?
Regards
|
|
|
| Re: access objects among plugins [message #200878 is a reply to message #200854] |
Wed, 21 March 2007 15:48  |
| Eclipse User |
|
|
|
Originally posted by: wharley.bea.com
"Nikita Mihalkov" <niki@email.ru> wrote in message
news:45c84bcffc4678cd287afd39222656e6$1@www.eclipse.org...
> Given 2 plugins A and B, I want to access a data member, or call a method
> of class reziding in plugin A from plugin B.
>
> Is it possible to do this?
If B depends on A, then it is just as if they were in the same plugin.
If A depends on B, but not B on A, then you need to access A indirectly via
an extension point.
If there is no dependency relationship, then it is not accessible.
|
|
|
| Re: access objects among plugins [message #200886 is a reply to message #200878] |
Wed, 21 March 2007 15:57 |
| Eclipse User |
|
|
|
Originally posted by: wharley.bea.com
"Walter Harley" <wharley@bea.com> wrote in message
news:etrk43$a38$1@utils.eclipse.org...
> If B depends on A, then it is just as if they were in the same plugin.
>
> If A depends on B, but not B on A, then you need to access A indirectly
> via an extension point.
>
> If there is no dependency relationship, then it is not accessible.
Whoops, forgot to mention one more caveat: a plug-in can also use its
manifest.mf to mark its items as exported or not, and it can selectively
export them to specific other plug-ins. So it also depends on whether A's
items are exported.
|
|
|
|
| Re: access objects among plugins [message #202709 is a reply to message #200886] |
Mon, 02 April 2007 08:23 |
| Eclipse User |
|
|
|
Originally posted by: viktor_sch.inbox.ru
And do not forget to update classpath by your plugin's PDE context submenu
after you export something or add it into classpath list. I was wondering
why eclipse environment doesn't do it by itself. That missunderstanding was
worth much time I missed.
"Walter Harley" <wharley@bea.com> wrote in message
news:etrkl8$hq5$1@utils.eclipse.org...
> "Walter Harley" <wharley@bea.com> wrote in message
> news:etrk43$a38$1@utils.eclipse.org...
>> If B depends on A, then it is just as if they were in the same plugin.
>>
>> If A depends on B, but not B on A, then you need to access A indirectly
>> via an extension point.
>>
>> If there is no dependency relationship, then it is not accessible.
>
> Whoops, forgot to mention one more caveat: a plug-in can also use its
> manifest.mf to mark its items as exported or not, and it can selectively
> export them to specific other plug-ins. So it also depends on whether A's
> items are exported.
>
|
|
|
Powered by
FUDForum. Page generated in 0.08866 seconds
] 
Search
Help
Register
Login
Home
