Eclipse Community Forums: Equinox » Remote provisioning

Help

Home

Home » Eclipse Projects » Equinox » Remote provisioning

Show: Today's Messages :: Show Polls :: Message Navigator

Remote provisioning [message #109247]

Thu, 08 May 2008 09:11

Eugen Reiswich

Messages: 35
Registered: July 2009

Member

Hi,

I'm developing an application which is supposed to upate, install and
remove plugins/features on a remote computer. Basically I'm trying to
merge the Eclipse communication framework with some update functionality.

I've arrived now at a point where I need an advise. The application I will
have to remote-update is a 24/7 application and is supposed never to be
stopped or restarted.

1. I started with the OSGi BundleContext, which is supposed to manage hot
plug installation etc. But I've read that by doing it in this way new
extensions and extension points in the plugin I've installed won't be
registered in the eclipse extension registry though the new plugin's
functionality won't be available to other plugins bevore a restart. Is
that really how it works?

2. Afterwards I've tried to use the Eclipse 3.3 update functionality which
is not hot plug able but can handle remote update sites etc. But now I've
read, that the usual update manager in Eclipse 3.3 will be replaces by
Equinox P2 in Eclipse 3.4. I either wasn't able to find any API for P2 or
some examples.

By now I have no idea how to go on!

Report message to a moderator

Re: Remote provisioning [message #109661 is a reply to message #109247]

Wed, 14 May 2008 02:42

Pascal Rapicault

Messages: 333
Registered: July 2009
Location: Ottawa

Senior Member

> 1. I started with the OSGi BundleContext, which is supposed to manage hot
> plug installation etc. But I've read that by doing it in this way new
> extensions and extension points in the plugin I've installed won't be
> registered in the eclipse extension registry though the new plugin's
> functionality won't be available to other plugins bevore a restart. Is
> that really how it works?
You can't trust everything you read on the internet :-) Upon
installation of new bundles, the extension point will update its state and
send deltas around.
The difficulty in being completely dynamic reside in the management it
requires in dealing with references you have from other plugins.
You also have to know that even though the workbench can react to
installation / uninstallation of plug-ins contributing to its extensions
(e.g. views), it does not allow for some of the plug-ins it depends on to be
updated.

>
> 2. Afterwards I've tried to use the Eclipse 3.3 update functionality which
> is not hot plug able but can handle remote update sites etc. But now I've
> read, that the usual update manager in Eclipse 3.3 will be replaces by
> Equinox P2 in Eclipse 3.4. I either wasn't able to find any API for P2 or
> some examples.
p2 is new in the SDK since M6. If you are looking at performing some
operations like install / uninstall / update, then you should take a look at
the org.eclipse.equinox.internal.provisional.p2.director.IDirect or
interface. Note that all packages with the word "provisional" in them are
things that we hope to make API in the next release. However for 1.0 there
is no official API.

HTH,

PaScaL

Report message to a moderator

Re: Remote provisioning [message #110102 is a reply to message #109661]

Thu, 15 May 2008 10:46

Eugen Reiswich

Messages: 35
Registered: July 2009

Member

Thanks PaScaL,

you've been a great help! I'll try to become familiar with Equinox p2 and
the org.eclipse.equinox.internal.provisional.p2.director.IDirect or.

Regards,
Eugen

Report message to a moderator

Previous Topic:	Troubleshooting OSGi jar wrapping
Next Topic:	Buddy class loading

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 25 16:16:42 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter