You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2021/11/26 15:05:00 UTC

[jira] [Resolved] (SLING-10498) MockConfiguration#delete() does not delete the configuration (still found by ConfigurationAdmin)

     [ https://issues.apache.org/jira/browse/SLING-10498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Konrad Windszus resolved SLING-10498.
-------------------------------------
    Resolution: Fixed

Fixed in https://github.com/apache/sling-org-apache-sling-testing-osgi-mock/commit/7be9cca77ae227081b2b15959b374a6eb334e5c8.

> MockConfiguration#delete() does not delete the configuration (still found by ConfigurationAdmin)
> ------------------------------------------------------------------------------------------------
>
>                 Key: SLING-10498
>                 URL: https://issues.apache.org/jira/browse/SLING-10498
>             Project: Sling
>          Issue Type: Improvement
>          Components: Testing
>    Affects Versions: Testing OSGi Mock 3.1.2
>            Reporter: Henry Kuijpers
>            Assignee: Konrad Windszus
>            Priority: Major
>             Fix For: Testing OSGi Mock 3.1.6
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> MockConfiguration#delete does not delete the configuration from the map (in MockConfigurationAdmin), but instead clears the properties of the configuration (while maintaining the PID).
> To mimic a real world scenario, that configuration should in fact be deleted from the map that MockConfigurationAdmin is holding.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)