[SLING-7193] osgi-mock: MockServiceReferences.compareTo reverses ordering

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Testing OSGi Mock 1.9.6, Testing OSGi Mock 2.3.2
• Fix Version/s: Testing OSGi Mock 1.9.8, Testing OSGi Mock 2.3.4
• Component/s: Testing
• Labels: mocks
• Assignee: Stefan Seifert
• Reporter: Stefan Seifert
• Created: 12/Oct/17 14:48
• Updated: 04/Feb/21 18:52
• Resolved: 12/Oct/17 15:47

Description

according to specification the compareTo method of the OSGi Framework ServiceReference implementation should implement an ascending ordering, with lowest ranking/highest service id first.

in osgi-mock this is contrary - highest ranking/lowest service id first. this has no effect on the MockBundleContext.getServiceReference method - this correctly returns the service with the highest ranking/lowest service id.

Issue Links

• is related to: SLING-10124 OSGi Mock - Service reference order is not correct for Collection field injection
• supercedes: SLING-7196 sling-mock: Make sure SlingContext.registerAdapter can overlay built-in adaptions