[
https://issues.apache.org/jira/browse/SLING-13292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Sedding resolved SLING-13292.
------------------------------------
Fix Version/s: Servlets Resolver 3.0.10
Resolution: Fixed
> Support ranking of bundles contributing bundled scripts
> -------------------------------------------------------
>
> Key: SLING-13292
> URL: https://issues.apache.org/jira/browse/SLING-13292
> Project: Sling
> Issue Type: New Feature
> Components: Servlets
> Affects Versions: Servlets Resolver 3.0.8
> Reporter: Julian Sedding
> Assignee: Julian Sedding
> Priority: Minor
> Fix For: Servlets Resolver 3.0.10
>
>
> When two or more bundles contain bundled scripts for the same paths, it is
> necessary to have a way to break the tie, ensuring a predictable and
> controlled precedence order.
> The current implementation selects the script with the lowest service.id,
> which in practice means the scripts provided by the bundle that was started
> earlier.
> This is counter-intuitive, e.g. in a development situation, where developers
> are usually interested in seeing their latest installed changes.
> It also links the script resolution precedence order to the start-order of
> the bundles, which can be a challenge in a dynamic system.
> In order to allow for a clearly defined resolution in such cases, it would be
> good to have an (optional) new bundle manifest header,
> {{{}Sling-Bundled-Scripts-Ranking{}}}, that defines the {{service.ranking}}
> to be set for each {{Servlet}} registered for the bundle.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
