[SLING-10124] OSGi Mock - Service reference order is not correct for Collection field injection

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Testing OSGi Mock 3.0.0
• Fix Version/s: Testing OSGi Mock 3.1.0
• Component/s: Testing
• Assignee: Stefan Seifert
• Reporter: Roy Teeuwen
• Created: 03/Feb/21 17:10
• Updated: 12/Mar/21 19:55
• Resolved: 08/Mar/21 12:25

Description

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

Issue Links

• relates to: SLING-7193 osgi-mock: MockServiceReferences.compareTo reverses ordering