Skip to main content



      Home
Home » Eclipse Projects » Equinox » Updating bundles
Updating bundles [message #51554] Mon, 24 October 2005 13:19 Go to next message
Eclipse UserFriend
I'm currently doing a little evaluation of Eclipse OSGi and have a few
questions :)

We want to be able to deploy updates to bundles to a central location
and all the various systems on our network running OSGi to be able to
see there is a new version of bundles available and download/install/run
them.

From my (quick) reading of the spec it doesn't seem like this is a
off-the-shelf behavior, I would have to find/implement a solution that
would notice the packages (on the remote web server) have been updated.

Naturally I'm very lazy and would rather use something that has already
been written! I've done a little digging and been able to find a
Knopflerfish and also Oscar "Bundle Repository".

So I guess my questions are:
1. Does Equinox already do what I want it to do?
2. Does Equinox also have a "Bundle Repository" ?
3. What is the risk in using non-Equinox bundles? (when using the
Equinox base OSGi implementation)
4. Does my auto-downloading of updated remote bundles scenario seems as
reasonable and trouble free to you as it does to me? :)
Re: Updating bundles [message #51578 is a reply to message #51554] Mon, 24 October 2005 18:32 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: pascal.ibm.canada

I don't know for sure about oscar bundle repository or knopflerfish but
I don't remember seeing any polling mechanism there.

1. In eclipse, the closest thing available comes with the update
scheduler. Update scheduler relies on the eclipse update technology.
Update delivers group of bundles (aka features) from "an update site"
(the server does not run anything special, it is just a URL to which you
connect to and where you can find a site.xml (a file listing the
features and plugins available)). Note that update does not use the
BundleContext.update but instead does a uninstall and then an install
(we hope to get that fixed in 3.2).

2. It is something we are considering

3. Getting too much for free :-). More seriously, as long as all the
bundles you want to use are playing by the API rule, then there is no
risk. Not more that you would have running those bundles on oscar or
knoplerfish.

4. Conceptually it is fine but coding an application that is completly
dynamic is not trivial.

PaScaL

RefuX wrote:
> I'm currently doing a little evaluation of Eclipse OSGi and have a few
> questions :)
>
> We want to be able to deploy updates to bundles to a central location
> and all the various systems on our network running OSGi to be able to
> see there is a new version of bundles available and download/install/run
> them.
>
> From my (quick) reading of the spec it doesn't seem like this is a
> off-the-shelf behavior, I would have to find/implement a solution that
> would notice the packages (on the remote web server) have been updated.
>
> Naturally I'm very lazy and would rather use something that has already
> been written! I've done a little digging and been able to find a
> Knopflerfish and also Oscar "Bundle Repository".
>
> So I guess my questions are:
> 1. Does Equinox already do what I want it to do?
> 2. Does Equinox also have a "Bundle Repository" ?
> 3. What is the risk in using non-Equinox bundles? (when using the
> Equinox base OSGi implementation)
> 4. Does my auto-downloading of updated remote bundles scenario seems as
> reasonable and trouble free to you as it does to me? :)
Re: Updating bundles [message #51736 is a reply to message #51554] Wed, 26 October 2005 21:09 Go to previous message
Eclipse UserFriend
Originally posted by: jeff_nospam_mcaffer.ca.ibm.com

Keep in mind that one of the benefits of OSGi is commonality. Common OSGi
provisioning mechansims should work on the Equinox framework. Eclipse's
Update mechanism uses some containerisms of Equinox to get better behaviour
(e.g., sharing of bundles between configurations) but we would certainly be
open to help in making it more flexible.

Jeff

"RefuX" <refux@hotmail.com> wrote in message
news:djj51a$d6$1@news.eclipse.org...
> I'm currently doing a little evaluation of Eclipse OSGi and have a few
> questions :)
>
> We want to be able to deploy updates to bundles to a central location
> and all the various systems on our network running OSGi to be able to
> see there is a new version of bundles available and download/install/run
> them.
>
> From my (quick) reading of the spec it doesn't seem like this is a
> off-the-shelf behavior, I would have to find/implement a solution that
> would notice the packages (on the remote web server) have been updated.
>
> Naturally I'm very lazy and would rather use something that has already
> been written! I've done a little digging and been able to find a
> Knopflerfish and also Oscar "Bundle Repository".
>
> So I guess my questions are:
> 1. Does Equinox already do what I want it to do?
> 2. Does Equinox also have a "Bundle Repository" ?
> 3. What is the risk in using non-Equinox bundles? (when using the
> Equinox base OSGi implementation)
> 4. Does my auto-downloading of updated remote bundles scenario seems as
> reasonable and trouble free to you as it does to me? :)
Previous Topic:Quick Start Guide
Next Topic:Initial bundles in eclipse
Goto Forum:
  


Current Time: Thu Jul 17 04:07:51 EDT 2025

Powered by FUDForum. Page generated in 0.10286 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top