Eclipse Community Forums: Remote Application Platform (RAP)

Home » Eclipse Projects » Remote Application Platform (RAP) » Handling bundle lifecycle?

Handling bundle lifecycle? [message #33399]

Thu, 14 June 2007 10:15

Eclipse User

What is the expected behavior when a running bundle that defines
extension points is stopped? For example, let's say I have a plugin
that defines a perspective and two views. When I stop the plugin from
the Equinox console I'd expect the perspective and views to disappear.
I'd also expect the perspective and views to become available when I
restart the bundle/plugin.

Is there defined behavior in these situations?

-Aaron

Re: Handling bundle lifecycle? [message #33895 is a reply to message #33399]

Mon, 18 June 2007 06:22

Eclipse User

Originally posted by: rherrmann.innoopract.com

From what I understand it is the responsibility of the plug-in to clean
up when shut down. This would include to close and release e.g. views
that are implemented by the plug-in.

But with RAP, due to its distributed nature, I doubt that this is an
easy task if ever possible at all.
Imagine a view that is opened from several sessions, then the plug-in is
shut down. And here lies problem: to close all instances of that view
and in addition realize that change client-side, you would need a
running request for every session the view is used in.

For a view to become available when a plug-in is started should be
possible. As we mainly copied the RCP Workbench code this works if it is
implemented there.

Rüdiger

Aaron Siri wrote:
> What is the expected behavior when a running bundle that defines
> extension points is stopped? For example, let's say I have a plugin
> that defines a perspective and two views. When I stop the plugin from
> the Equinox console I'd expect the perspective and views to disappear.
> I'd also expect the perspective and views to become available when I
> restart the bundle/plugin.
>
> Is there defined behavior in these situations?
>
> -Aaron

Re: Handling bundle lifecycle? [message #33924 is a reply to message #33895]

Mon, 18 June 2007 11:03

Eclipse User

It seems like you'd need to implement support for it in the ViewManager
(in the case of views.) It would have to detect if a bundle is being
stopped and then close/affect all of the extensions that it registered.
It is probably easier to do in a more pure OSGi environment (i.e.
using OSGi services vs. the registry/plugin.xml infrastructure) but
seems like it should be possible (I'm doing it in a custom
Eclipse-like framework that I have been working - a contingency if RAP
wasn't far enough along. Probably won't be an issue. ;)

-Aaron

Rüdiger Herrmann wrote:
> From what I understand it is the responsibility of the plug-in to clean
> up when shut down. This would include to close and release e.g. views
> that are implemented by the plug-in.
>
> But with RAP, due to its distributed nature, I doubt that this is an
> easy task if ever possible at all.
> Imagine a view that is opened from several sessions, then the plug-in is
> shut down. And here lies problem: to close all instances of that view
> and in addition realize that change client-side, you would need a
> running request for every session the view is used in.
>
> For a view to become available when a plug-in is started should be
> possible. As we mainly copied the RCP Workbench code this works if it is
> implemented there.
>
> Rüdiger
>
>
> Aaron Siri wrote:
>> What is the expected behavior when a running bundle that defines
>> extension points is stopped? For example, let's say I have a plugin
>> that defines a perspective and two views. When I stop the plugin from
>> the Equinox console I'd expect the perspective and views to disappear.
>> I'd also expect the perspective and views to become available when I
>> restart the bundle/plugin.
>>
>> Is there defined behavior in these situations?
>>
>> -Aaron

Previous Topic:	how to start unit test inside the ide since RAP M4
Next Topic:	Editor support ported

Goto Forum:

-=] Back to Top [=-

Current Time: Thu Jul 03 11:05:54 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter