felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Watson (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (FELIX-5514) Issues with substituted exports with require bundle
Date Thu, 09 Feb 2017 17:48:42 GMT

     [ https://issues.apache.org/jira/browse/FELIX-5514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Thomas Watson resolved FELIX-5514.
    Resolution: Fixed

I fixed this by keeping track of substitutions in the resolver for resources it is resolving.
 For resources that have existing wirings I added a new method to FelixResolveContext called
getSubstitutionWires so that the resolve doesn't have to recalculate this in cases where the
resolve context already keeps track of it.

> Issues with substituted exports with require bundle
> ---------------------------------------------------
>                 Key: FELIX-5514
>                 URL: https://issues.apache.org/jira/browse/FELIX-5514
>             Project: Felix
>          Issue Type: Bug
>          Components: Resolver
>         Environment: All
>            Reporter: Thomas Watson
>            Assignee: Thomas Watson
> When resolving require-bundle requirements there is an issue if the bundle being required
has substituted exports.  The issue is that any requiring bundle will not have the export
substituted included in their own class space.  At runtime the OSGi core specification requires
that substituted exports be accessible to requiring bundles.  This can cause issues in the
consistency check done by the resolver because the class space the requiring bundle will be
missing packages that should be visible.
> The resolver needs to keep track of substituted exports and make sure to include any
substitutions in the class spaces of the requiring bundles.

This message was sent by Atlassian JIRA

View raw message