felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Bosschaert (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (FELIX-5049) Resolver does not choose the revision with the lowest bundle ID
Date Tue, 06 Oct 2015 15:40:26 GMT

    [ https://issues.apache.org/jira/browse/FELIX-5049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14945140#comment-14945140
] 

David Bosschaert edited comment on FELIX-5049 at 10/6/15 3:39 PM:
------------------------------------------------------------------

Hi [~rickhall], I see your point. I guess this is really around the fact that the Framework
cannot provide a substitutable import to the {{org.osgi.service.resolver}} package and import
that package to achieve a single class-space. 

Two further thoughts to consider:
1. We could make the framework special such that if a package is exported from the framework
then that will take precedence over other exporters in case of such a close tie (i.e. change
my proposed patch to not look at the number of services but to prefer a framework-provided
package in such situation).
-2. Another option would be to provide the resolver service in a separate bundle rather than
directly from the framework bundle and then ship that bundle as part of the default.-
Actually, I've removed option 2 here as I think this won't work unless we revert to reflection.
The resolver service will have to have access to the framework resolver implementation. If
these end up being in a different class-space if can't access those, so I think this is not
a potential possibility.

Option 1 above is left? How about it?


was (Author: bosschaert):
Hi [~rickhall], I see your point. I guess this is really around the fact that the Framework
cannot provide a substitutable import to the {{org.osgi.service.resolver}} package and import
that package to achieve a single class-space. 

Two further thoughts to consider:
1. We could make the framework special such that if a package is exported from the framework
then that will take precedence over other exporters in case of such a close tie (i.e. change
my proposed patch to not look at the number of services but to prefer a framework-provided
package in such situation).
2. Another option would be to provide the resolver service in a separate bundle rather than
directly from the framework bundle and then ship that bundle as part of the default.

> Resolver does not choose the revision with the lowest bundle ID
> ---------------------------------------------------------------
>
>                 Key: FELIX-5049
>                 URL: https://issues.apache.org/jira/browse/FELIX-5049
>             Project: Felix
>          Issue Type: Bug
>          Components: Resolver
>    Affects Versions: framework-5.2.0
>            Reporter: David Bosschaert
>            Assignee: David Bosschaert
>         Attachments: felix-5049.diff
>
>
> The Felix Resolver does not pick the exporting bundle with the lowest bundle ID when
multiple bundles export the same package. This causes [ARIES-1398|https://issues.apache.org/jira/browse/ARIES-1398].
For steps on how to reproduce see that issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message