[
https://issues.apache.org/jira/browse/SLING-5886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15389467#comment-15389467
]
Carsten Ziegeler commented on SLING-5886:
-----------------------------------------
[[email protected]] I like the name ConfigurationResourceResolver and I
think it makes sense to keep the interfaces separate. I personally would even
put them in different packages, as most users are just interested in the
ConfigurationResolver to get configurations. The CRR is just the low level
implementation doing most of the magic, and the CR is the higher level service.
There could be other services like the CR for example for workflows and they
would base the implementation in the CRR as well.
The CR is has methods to return a value map, I think we should only return
read-only configurations and make this clear in the javadocs. In my prototype I
have the NamedValueMap (extends ValueMap) in order to have a way to return the
config name. Another option would be to include the name in the value map as a
predefined key.
I personally don't like the method names "get" and "getList" as by just looking
at these names it's not clear what they do, but if I'm the only one we can go
with these.
For the CRR, I'm slightly unsure what getContextPath, getAllContextPaths does.
Is it correct that the input is e.g. a content resource from
"/content/foo/bar"? And the returned path is the first path where the
implementation would look for configurations?
> 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)
