[
https://issues.apache.org/jira/browse/SLING-5664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15245307#comment-15245307
]
Bertrand Delacretaz commented on SLING-5664:
--------------------------------------------
bq. I had to remove usage of SlingScriptHelper in the injector completely...
I suppose there is a reason for {{OSGiServiceInjector}} to use either
{{SlingScriptHelper}} or {{BundleContext}} to get services, it would be good to
find out what that reason is before removing the use of {{SlingScriptHelper}}.
The alternative is to require SLING-5665 which would (IIUC) allow to keep using
{{SlingScriptHelper}}.
> Models: OSGiServiceInjector does not consider service.ranking
> -------------------------------------------------------------
>
> Key: SLING-5664
> URL: https://issues.apache.org/jira/browse/SLING-5664
> Project: Sling
> Issue Type: Bug
> Components: Extensions
> Affects Versions: Sling Models Impl 1.2.6
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Fix For: Sling Models Impl 1.2.8
>
> Attachments: SLING-5664-v01.patch
>
>
> The injector is using {{BundleContext.getServiceReferences(Class, String)}}
> or {{SlingScriptHelper.getServices(Class, String)}}
> (https://github.com/apache/sling/blob/trunk/bundles/extensions/models/impl/src/main/java/org/apache/sling/models/impl/injectors/OSGiServiceInjector.java#L97).
> From the returned array it just takes the first item.
> Unfortunately the order in that array is not-deterministic, especially it is
> not necessarily that way that items with a higher service.ranking are
> returned first.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
