Stefan Seifert updated SLING-6026:
    Fix Version/s:     (was: Context-Aware Configuration API 1.0.0)
                   Context-Aware Configuration Impl 1.0.0
                   Context-Aware Configuration SPI 1.0.0

> Context-Aware Config: Pluggable configuration persistence
> ---------------------------------------------------------
>                 Key: SLING-6026
>                 URL: https://issues.apache.org/jira/browse/SLING-6026
>             Project: Sling
>          Issue Type: New Feature
>          Components: Extensions
>            Reporter: Stefan Seifert
>            Assignee: Stefan Seifert
>              Labels: contextaware-config
>             Fix For: Context-Aware Configuration SPI 1.0.0, Context-Aware 
> Configuration Impl 1.0.0
> currently configuration data is only read, and it's hard-coded how it's 
> stored in the configuration resource (properties directly in the resource).
> we need to enhance this to provide a management API to read+write 
> configuration data (required for configuration editor GUIs).
> additional the details of the persistence should be pluggable with a simple 
> default implementation which can be similar to what is present today. but in 
> more complex environments it may be desired to:
> * use special node types to store the configuration in (e.g. to make sure 
> they are stored in an index)
> * use a jcr:content subnode to store configuration data in
> * assign special resource types to support a configuration editor
> * decide in which path the configurations are stored

This message was sent by Atlassian JIRA

Reply via email to