[
https://issues.apache.org/jira/browse/GERONIMO-5786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12992366#comment-12992366
]
David Jencks commented on GERONIMO-5786:
----------------------------------------
The osgi spec 3.6 says
The following list defines the preferences, if multiple choices are possible,
in order of decreasing priority:
• A resolved exporter must be preferred over an unresolved exporter.
• An exporter with a higher version is preferred over an exporter with a
lower version.
• An exporter with a lower bundle ID is preferred over a bundle with a
higher ID.
In my experiments so far these seem to be followed. No package exports have
versions. I created a bundle with the same symbolic name as the one in the eba
and a higher bundle version. When deployed it had a higher bundle id 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)
> Components: osgi
> Affects Versions: 3.0-M2, 3.0
> Reporter: viola.lu
> Priority: Minor
> Fix For: 3.0-M2, 3.0
>
>
> - deploy an EBA: [email protected] = [email protected] + [email protected]
> - add bundle v1.0.1 via osgi:install [email protected]
> My expectation was that if I did osgi:refresh [WAB] it would re-resolve and
> pick up the new bundle (1.0.1). Instead, I find that I need to do
> osgi:refresh TWICE for it to pick up the new bundle version!
> 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...
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
