[jira] [Resolved] (SLING-5886) Sling Context-Aware Configuration - Initial Contribution

["Stefan Seifert (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-5886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Seifert resolved SLING-5886.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: Context-Aware Configuration 1.0.0

thanks carsten for submitting this part. i did some more cosmetic refactorings and renamings yesterday and today. most relevant changes are:
* first simple set of integration tests added
* updated unit tests to cover more conversion cases already supported by the osgi converter service
* subtle change to ConfiguraitonBuilder API: my goal is that that the "as" conversion method never returns null, to avoid constantly checking for null when accessing it. (the @NonNull annotation already that this, but the javadoc said another and the impl could return null). my goal is to return an empty annotation class/with default values in this case. only if even the conversion of an empty map fails (e.g. target class is invalid and cannot be instantiated at all) a runtime exception is thrown. if we need further discussion on this perhaps in a separate ticket.
* currently ConversionExceptions from the osgi converter may get through to the upstream code. we may want to prevent this, but this would be another ticket.

i will set this ticket to resolved, further work (and a lot is left) will continue in separate tickets.

> Sling Context-Aware 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
>              Labels: contextaware-config
>             Fix For: Context-Aware Configuration 1.0.0
>
>
> 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
> _Update: as discussed at http://sling.markmail.org/thread/ka3ewlswfgjy7rpu the name of this new module is Context-Aware Configuration_



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)