Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Date: Wed, 9 Feb 2011 07:49:57 +0000 (UTC)
From: "David Jencks (JIRA)" <jira@apache.org>
To: dev@geronimo.apache.org
Message-ID: 
 <1666215454.4535.1297237797475.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: <24968408.213271296042945041.JavaMail.jira@thor>
Subject: [jira] Commented: (GERONIMO-5786) The double refresh problem with
 EBAs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/GERONIMO-5786?page=3Dcom.atlass=
ian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1=
2992366#comment-12992366 ]=20

David Jencks commented on GERONIMO-5786:
----------------------------------------

The osgi spec 3.6 says

The following list defines the preferences, if multiple choices are possibl=
e, in order of decreasing priority:
=E2=80=A2=09A resolved exporter must be preferred over an unresolved export=
er.=20
=E2=80=A2=09An exporter with a higher version is preferred over an exporter=
 with a
lower version.=20
=E2=80=A2=09An exporter with a lower bundle ID is preferred over a bundle w=
ith a
higher ID.

In my experiments so far these seem to be followed.  No package exports hav=
e versions.  I created a bundle with the same symbolic name as the one in t=
he eba and a higher bundle version.  When deployed it had a higher bundle i=
d than the bundle from the eba.  In order to get resolve to pick up the new=
 bundle I had to uninstall the eba's bundle with the lower bundle id.

Next I will try using a export package version.


> The double refresh problem with EBAs
> ------------------------------------
>
>                 Key: GERONIMO-5786
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-5786
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues)=20
>          Components: osgi
>    Affects Versions: 3.0-M2, 3.0
>            Reporter: viola.lu
>            Priority: Minor
>             Fix For: 3.0-M2, 3.0
>
>
> - deploy an EBA: A@1.0.0 =3D WAB@1.0.0 + bundle@1.0.0
> - add bundle v1.0.1 via osgi:install bundle@1.0.1
> My expectation was that if I did osgi:refresh [WAB] it would re-resolve a=
nd pick up the new bundle (1.0.1). Instead, I find that I need to do osgi:r=
efresh TWICE for it to pick up the new bundle version!=C2=A0
> If the WAB was deployed as a standalone entity outside EBA, then it takes=
 only one osgi:refresh for it to pick up the new dependent bundle version..=
.

--=20
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira