You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "A. J. David Bosschaert (Jira)" <ji...@apache.org> on 2020/05/01 09:12:00 UTC
[jira] [Closed] (SLING-9395) Support bundle updates in api regions
[ https://issues.apache.org/jira/browse/SLING-9395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
A. J. David Bosschaert closed SLING-9395.
-----------------------------------------
> Support bundle updates in api regions
> -------------------------------------
>
> Key: SLING-9395
> URL: https://issues.apache.org/jira/browse/SLING-9395
> Project: Sling
> Issue Type: Improvement
> Components: Feature Model
> Reporter: Carsten Ziegeler
> Assignee: A. J. David Bosschaert
> Priority: Major
> Fix For: Feature Model API Regions Runtime Fragment 1.1.0
>
>
> API Regions don't support bundles being updated dynamically, which is something that is sometimes needed to try out newly developed functionality or bugfixes.
> To address use cases in this area, we need to allow bundles being updated to a different version than the one specified initially with the API Regions as long as the bundle location stays the same.
> The algorithm to find what feature a bundle belongs to at runtime will become the following:
> 1. Find the feature a bundle belongs to by looking up the bundle-location association with the feature.
> 2. If the bundle location is not associated to a feature yet, look up the bsn+version from the initial, defined list, and associate the new bundle location with the feature found there.
> This approach is similar to how OSGi ConfigAdmin associates a bundle location with a configuration.
> This approach also needs to take into account that package imports and exports of the bundle might change, like new imports for a newer version
--
This message was sent by Atlassian Jira
(v8.3.4#803005)