You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Stefan Seifert (Jira)" <ji...@apache.org> on 2021/12/16 16:54:00 UTC

[jira] [Updated] (SLING-11019) Nested sub configurations in nested configuration collections: Config name not correctly applied from persistence strategy

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

Stefan Seifert updated SLING-11019:
-----------------------------------
    Summary: Nested sub configurations in nested configuration collections: Config name not correctly applied from persistence strategy  (was: Nested sub configurations in nested configuration collections: Config name not currect applied from persistence strategy)

> Nested sub configurations in nested configuration collections: Config name not correctly applied from persistence strategy
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SLING-11019
>                 URL: https://issues.apache.org/jira/browse/SLING-11019
>             Project: Sling
>          Issue Type: Bug
>          Components: Extensions
>    Affects Versions: Context-Aware Configuration Impl 1.5.0
>            Reporter: Stefan Seifert
>            Assignee: Stefan Seifert
>            Priority: Major
>             Fix For: Context-Aware Configuration Impl 1.6.0
>
>
> background and test case for this issue: https://wcm-io.atlassian.net/browse/WCON-87
> via custom implementations of ConfigurationPersistenceStrategy2 it is possible to apply additional sub nodes for either config resources, collection resource parents or collection items. in special case with nested sub configuration within a nested configuration list this was not applied in the correct order.



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