Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Virgo » Issue with Version range in Import package(latest bundle version packages not getting referred in other bundles when imported using version range.)
Issue with Version range in Import package [message #872052] Tue, 15 May 2012 07:37 Go to next message
Obiwan Kenobi is currently offline Obiwan Kenobi
Messages: 8
Registered: March 2012
Junior Member
Hi All,

Here is what is happening to me...

I have an existing bundle hello-1.1.0 up and running in Virgo.
in its Export package manifest header the package is mentioned as com.test.hello;version="1.0.0";

I make a change in com.test.hello package and increase the version of bundle and package to 1.2.0 and deployed the new bundle hello-1.2.0 and version of package in that bundle manifest is com.test.hello;version="1.2.0"

One of my other bundle which was a consumer of com.test.hello has the Import package manifest header as
com.test.hello;version="[1.0.0,2.0.0)" the version range.

Will the consumer bundle automatically able to pickup the version 1.2.0 since I have mentioned the version range?

It was not happening to me.The consumer bundle was still referring to the package com.test.hello from hello-1.1.0 and not hello-1.2.0

I refreshed my consumer bundle once from virgo console and after which the package was getting reffered from hello-1.2.0.

How does this version range actually works.? Do I need to refresh my consumer bundles every time I deploy a new service bundles?

Any help on this is appreciated.

Regards
Re: Issue with Version range in Import package [message #872643 is a reply to message #872052] Wed, 16 May 2012 10:09 Go to previous message
Hristo Iliev is currently offline Hristo Iliev
Messages: 156
Registered: May 2010
Location: Sofia, Bulgaria
Senior Member

According to the OSGi spec ("Updating Bundles"):

Quote:
The update process supports migration from one version of a bundle to a
newer version of the same bundle. The exports of an updated bundle must
be immediately available to the Framework. If none of the old exports are
used, then the old exports must be removed. Otherwise, all old exports must
remain available for existing bundles and future resolves until the
refreshPackages method is called or the Framework is restarted.


Refresh is therefore needed in order to have the wiring as you want it.
Previous Topic:Virgo hangs when stopping web bundle
Next Topic:Why does plan deplyment fails when uploading from the web console?
Goto Forum:
  


Current Time: Fri Apr 18 01:46:16 EDT 2014

Powered by FUDForum. Page generated in 0.01486 seconds