[
https://issues.apache.org/jira/browse/SLING-5886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15392651#comment-15392651
]
Carsten Ziegeler commented on SLING-5886:
-----------------------------------------
I'm fine with just returning a ValueMap and not a named value map or adding the
name as a special property to the value map.
Yes, looking at "get" and "getList" its not clear what they do and I totally
agree with not using "resolve...." (I came to the same conclusion after my
prototype).
I've thought a little bit about the methods for custom annotation classes -
while I see that the default mapping is the class name and there could be some
annotation on that class, this basically means that you can only have one
configuration of that type. However, e.g. if you think about server
configurations (url, user, password) you might have several of them all using
the same custom annotation class. So I have the feeling that we should have a
variant where you pass in the class and the name.
> 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)
