[jira] [Commented] (KARAF-888) Add a Karaf Config Service

["Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KARAF-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13112404#comment-13112404 ] 

Jean-Baptiste Onofré commented on KARAF-888:
--------------------------------------------

I think I wasn't clear in my previous comment.

The Karaf Config Service is only responsible of the ConfigAdmin storage, and it implements the PersistenceManager ConfigAdmin interface.

> Add a Karaf Config Service
> --------------------------
>
>                 Key: KARAF-888
>                 URL: https://issues.apache.org/jira/browse/KARAF-888
>             Project: Karaf
>          Issue Type: Improvement
>          Components: karaf-config
>            Reporter: Jean-Baptiste Onofré
>             Fix For: 3.0.0
>
>
> Up to now, Karaf uses Felix FileInstall to poll files in the etc folder and load the properties containing in the files (the files respect the pid.cfg format) in the ConfigAdmin service.
> On the other hand, Karaf manipulate ConfigAdmin via the config:* commands and is able to flush back the properties in the files in this commands.
> I propose two improvements around ConfigAdmin:
> - we could create a Karaf Config Service on top of ConfigAdmin to be able to choose and change the storage backend of configuration. For instance, replace/concats the etc folder with a JDBC or LDAP backend. We could implement something similar to JAAS with a kind of ConfigModule.
> - the config:* commands shouldn't be responsible to writing the files. The config:* commands could use the Karaf Config Service. The Karaf Config Service will be responsible to updating the ConfigAdmin service, and flush the changes to the storage backend.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira