[
https://issues.apache.org/jira/browse/SLING-11066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17477666#comment-17477666
]
Carsten Ziegeler commented on SLING-11066:
------------------------------------------
The common solution is to ask the highest ranked provider first, so yes sorting
could be reversed or the array traversed from end to start
> Sort URIProvider references
> ---------------------------
>
> Key: SLING-11066
> URL: https://issues.apache.org/jira/browse/SLING-11066
> Project: Sling
> Issue Type: Bug
> Components: JCR
> Affects Versions: JCR Resource 3.1.0
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
> Fix For: JCR Resource 3.2.0
>
> Time Spent: 2h 40m
> Remaining Estimate: 0h
>
> If multiple URIProvider services are provided the order is currently
> non-deterministic due to the code in
> https://github.com/apache/sling-org-apache-sling-jcr-resource/blob/5af8c2bb5728184f22d3098967a57d5f1902789c/src/main/java/org/apache/sling/jcr/resource/internal/helper/jcr/JcrResourceProvider.java#L156-L168.
> Instead the implementations should be ordered according to the rules of
> https://docs.osgi.org/javadoc/osgi.core/8.0.0/org/osgi/framework/ServiceReference.html#compareTo-java.lang.Object-
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
