karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré (JIRA) <j...@apache.org>
Subject [jira] [Updated] (KARAF-888) Add a Karaf Config Service
Date Wed, 21 Sep 2011 19:15:14 GMT

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

Jean-Baptiste Onofré updated KARAF-888:

    Summary: Add a Karaf Config Service  (was: Add a service layer for ConfigAdmin)

> 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
> 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


View raw message