[
https://issues.apache.org/jira/browse/SLING-13097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bart Thierens updated SLING-13097:
----------------------------------
Description:
When using a (collection of) reference(s) in a component, OSGi Mock will
automatically inject when calling SlingContext/AemContext's
registerService/registerInjectActivate.
When adding bind/unbind/update method to that reference, the mock context will
trigger perfectly the bind-methods, but the field 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 field being updated automatically.
was:
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.
> Mock OSGi does inject reference 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) reference(s) in a component, OSGi Mock will
> automatically inject when calling SlingContext/AemContext's
> registerService/registerInjectActivate.
> When adding bind/unbind/update method to that reference, the mock context
> will trigger perfectly the bind-methods, but the field 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 field being updated automatically.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
