I clarified the documentation in https://github.com/apache/sling-site/commit/cb12f47c7b55bd03ccf0951c112df68a40d67fd2 and added a link to https://docs.osgi.org/specification/osgi.core/8.0.0/framework.service.html#framework.service.servicerankingorder
The according code is IMHO in https://github.com/apache/sling-org-apache-sling-servlets-resolver/blob/1603a0ecb2ab8b4395560c0d53d9e5569b68a568/src/main/java/org/apache/sling/servlets/resolver/internal/resource/MergingServletResourceProvider.java#L107 Although additional test cases are obviously nice, I don’t think we need to change anything about the implementation. Konrad > On 11. May 2022, at 17:29, Bertrand Delacretaz <bdelacre...@apache.org> wrote: > > Hi, > > Le mer. 11 mai 2022 à 17:23, Carsten Ziegeler <cziege...@apache.org> a écrit : >> ...Service ranking is more predictable than just using the "first"... > > I agree, but what if two servlets have the exact same service > parameters including service ranking? > > That's what I think we should reject. > > -Bertrand
