[
https://issues.apache.org/jira/browse/SLING-5886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15389222#comment-15389222
]
Stefan Seifert commented on SLING-5886:
---------------------------------------
and the annotation class is also the vehicle to provide the whole block "B)
Describing configurations" listed in https://wcm-io.atlassian.net/wiki/x/BQBLAQ
like sling models when a bundle is starting with configuration annotation
classes in it an extender detects them, parses them, and the configuration
bundle "knows" which configuration metadata exists with what default values,
what labels/descriptions. the default values are important for resolving the
configuration, the labels/descriptions for any GUI that is provided to the user.
so the annotation classes both make reading configurations easier, and replace
the clumsy approach of defining parameter metadata in java classes holdling
lists of parameter constants like it was in wcm.io Config V1. internally they
are still mapped to parameter metadata classes for faster access without
reflection (some parts of it can already be seen in the SPI interfaces in my
prototoype, but the are still WIP).
> 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)
