You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bart Thierens (Jira)" <ji...@apache.org> on 2026/02/04 10:05:00 UTC
[jira] [Updated] (SLING-13097) Mock OSGi does inject reference when bind methods are present
[ https://issues.apache.org/jira/browse/SLING-13097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bart Thierens updated SLING-13097:
----------------------------------
Summary: Mock OSGi does inject reference when bind methods are present (was: Mock OSGi does inject reference collection when bind methods are present)
> 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 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)