[SLING-6372] OSGi Mocks - Correctly handle static, greedy references

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Testing OSGi Mock 1.9.0, Testing OSGi Mock 2.2.0
• Fix Version/s: Testing OSGi Mock 1.9.2, Testing OSGi Mock 2.2.2
• Component/s: Testing
• Labels: mocks
• Assignee: Stefan Seifert
• Reporter: Francesco Mari
• Created: 07/Dec/16 08:39
• Updated: 19/Dec/16 11:58
• Resolved: 12/Dec/16 15:30

Description

If a component A has a static, greedy reference to another component/service B (independently from the cardinality), A should react when new, better instances of B are registered.

Example. A has an optional, static, greedy reference to B. A is first registered and - being the reference optional - is correctly activated. Then, an instance of B is registered. A should be deactivated, its bind method for B should be called, and A should be activated again.

This behaviour is currently only supported for dynamic references, but I think it should be extended to static (and greedy) references too.

Issue Links

• blocks: OAK-5273 Reintroduce tests disabled or removed for OAK-5223