You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2024/11/06 14:09:00 UTC
[jira] [Commented] (SLING-12472) Sling Models Impl: Injector and Implementation Picker service ranking is reversed
[ https://issues.apache.org/jira/browse/SLING-12472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17895976#comment-17895976 ]
Konrad Windszus commented on SLING-12472:
-----------------------------------------
This has been clarified at least in the OSGi javadoc and spec meanwhile: https://github.com/osgi/osgi/issues/400...
> Sling Models Impl: Injector and Implementation Picker service ranking is reversed
> ---------------------------------------------------------------------------------
>
> Key: SLING-12472
> URL: https://issues.apache.org/jira/browse/SLING-12472
> Project: Sling
> Issue Type: Task
> Components: Sling Models
> Reporter: Stefan Seifert
> Assignee: Stefan Seifert
> Priority: Critical
>
> SLING-12374 switched the handling of registering multiple implementation pickers from "manual" via "RankedServices" to a more elegant pure DS solution. but this change introduced a severe bug:
> for historic/backward compatibility reasons, service ranking is interpreted "the wrong way" when registering implementation pickers, with highest ranking value = lowest ranking. lot of projects depend on this current behavior of sling models impl 1.7.0 and below.
> with 1.7.2 and the change from SLING-12374 this is reversed. this needs to be fixed to restore the previous behavior.
> Update: the ordering Injector implementation is affected in the same way
--
This message was sent by Atlassian Jira
(v8.20.10#820010)