Francesco Mari created SLING-6372:
-------------------------------------
Summary: OSGi Mocks - Correctly handle static, greedy references
Key: SLING-6372
URL: https://issues.apache.org/jira/browse/SLING-6372
Project: Sling
Issue Type: Improvement
Components: Testing
Reporter: Francesco Mari
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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
