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/22 22:30:00 UTC
[jira] [Resolved] (SLING-8849) CA Config HTL bindings value provider is too limited: Unable to influence the source of adaption
[ https://issues.apache.org/jira/browse/SLING-8849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Seifert resolved SLING-8849.
-----------------------------------
Resolution: Fixed
implemented:
* https://github.com/apache/sling-org-apache-sling-caconfig-spi/commit/20145572b40ac3a2177f948ad5053365b168cedb
* https://github.com/apache/sling-org-apache-sling-caconfig-impl/commit/5a1da1a80ed9d3677ba328c0cd5409bd0364f24f
* https://github.com/apache/sling-org-apache-sling-testing-caconfig-mock-plugin/commit/99e403d521d492d0e7f401c25775e13a281fbd94
> CA Config HTL bindings value provider is too limited: Unable to influence the source of adaption
> ------------------------------------------------------------------------------------------------
>
> Key: SLING-8849
> URL: https://issues.apache.org/jira/browse/SLING-8849
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: Context-Aware Configuration Impl 1.5.0
> Environment: AEM 6.x
> Reporter: Henry Kuijpers
> Assignee: Stefan Seifert
> Priority: Major
> Labels: pull-request-available
> Fix For: Context-Aware Configuration SPI 1.4.0, Context-Aware Configuration Impl 1.6.0, Context-Aware Configuration Mock Plugin 1.4.0
>
> Time Spent: 3h 20m
> Remaining Estimate: 0h
>
> The provided ConfigurationBindingsValueProvider is too limited, due to missing extension points: It would be beneficial for project implementations to be able to influence the source of adaption for the config. See also the implementation of the getBindings() method: [https://github.com/apache/sling-org-apache-sling-caconfig-impl/blob/master/src/main/java/org/apache/sling/caconfig/impl/ConfigurationBindingsValueProvider.java#L77].
> This should not be tied to the current resource necessarily, but instead be tied to the current resource by default, but leave options open for overriding this behavior i.e. in CMSes where you might want to use another object to to act as the determinator of the context.
> See also the discussion in: [https://wcm-io.atlassian.net/browse/WCON-75]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)