[
https://issues.apache.org/jira/browse/SLING-10124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17279069#comment-17279069
]
Stefan Seifert commented on SLING-10124:
----------------------------------------
this behavior was fixed exactly like this in SLING-7193.
i'm quite sure the current implementation is correct and in sync with the real
framework.
unfortunately SLING-7193 does not contain links to the relevant parts of the
OSGI spec.
> OSGi Mock - Service reference order is not correct
> --------------------------------------------------
>
> Key: SLING-10124
> URL: https://issues.apache.org/jira/browse/SLING-10124
> Project: Sling
> Issue Type: Bug
> Components: Testing
> Reporter: Roy Teeuwen
> Priority: Major
>
> If I look at the osgi mocks implementation to get back a list of service
> references, I have the feeling that the order is wrong:
> https://github.com/apache/sling-org-apache-sling-testing-osgi-mock/blob/ef6535bab69562ad3c2276dc84893fa2fab48438/core/src/main/java/org/apache/sling/testing/mock/osgi/MockBundleContext.java#L295
> It states here that the order is the reverse order, but if I check in the
> framework itself, the following comment would state the other order (which is
> what I also experience when debugging in a live instance) :
> https://github.com/apache/felix-dev/blob/c562829a9ffd40af2f165a8b4763b4d6759f3c0f/framework/src/main/java/org/apache/felix/framework/ServiceRegistrationImpl.java#L688
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
