[
https://issues.apache.org/jira/browse/SLING-13097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18056403#comment-18056403
]
Bart Thierens commented on SLING-13097:
---------------------------------------
Sample project to indicate the problem:
https://github.com/senn/sling-13097-osgi-mock-ref-update-bind
Should be easy to run (mvn test) and deploy to a Sling/AEM instance.
> Mock OSGi does inject reference collection when bind methods are present
> ------------------------------------------------------------------------
>
> Key: SLING-13097
> URL: https://issues.apache.org/jira/browse/SLING-13097
> Project: Sling
> Issue Type: Bug
> Components: Testing
> Affects Versions: Testing OSGi Mock 3.5.2
> Reporter: Bart Thierens
> Priority: Major
>
> When using a collection of references in a component, OSGi Mock will
> automatically add them to the reference-collection when calling
> SlingContext/AemContext's registerService.
> When adding bind/unbind/update method to that reference collection, the mock
> context will trigger perfectly the bind-methods, but the collection itself is
> never updated. It stays forever null.
> This is different from how OSGi does it. There I can see the bind methods
> being triggered + the collection being updated automatically.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
