[
https://issues.apache.org/jira/browse/SLING-5886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15389274#comment-15389274
]
Alexander Saar commented on SLING-5886:
---------------------------------------
from [1], it says "Allow overriding content-specific parameters via OSGi
configuration" in section F. not exactly sure what the use case here would be.
Imo we should think of configs in terms of delivery especially in the context
of a product like AEM. there are configs which are shipped ootb with the
product. some of those are overlayed by the integration partner/team or new
configs added during the project/deployment phase. finally some of them might
be changed /extended by end users as directly on the running system. something
like the workflow description Carsten mentioned above.
[1] https://wcm-io.atlassian.net/wiki/display/WCMIO/Configuration+Usecases
> Sling Configuration - Initial Contribution
> ------------------------------------------
>
> Key: SLING-5886
> URL: https://issues.apache.org/jira/browse/SLING-5886
> Project: Sling
> Issue Type: New Feature
> Components: Extensions
> Reporter: Stefan Seifert
> Assignee: Stefan Seifert
>
> as discussed in the mailing list (see [my post from april
> 2016|http://apache-sling.73963.n3.nabble.com/RT-Use-cases-for-content-specific-configurations-in-Sling-amp-Contribution-td4060813.html])
> i want to contribute the wcm.io Configuration parts that are not
> AEM-specific.
> the current features of wcm.io Configuration are described here:
> http://wcm.io/config/
> the main goal is to support "context-specific" configuration, that means
> configuration that is different for different content paths (e.g. sites,
> tenants).
> during the contribution some changes and refactorings are required/planned,
> e.g.:
> * remove some dependencies to wcm.io build environment, Guava and others
> * remove the "application" distinction currently part of wcm.io Configuration
> in favor or a more path-based distinction
> * refactor the user-faced configuration API to further simplify it and
> support OSGi R6-style annotation classed for typed configuration access
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
