You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Oliver Heger (JIRA)" <ji...@apache.org> on 2016/03/24 21:13:26 UTC
[jira] [Updated] (CONFIGURATION-498) Add OSGi Configuration Admin
Service as a source for configuration data
[ https://issues.apache.org/jira/browse/CONFIGURATION-498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oliver Heger updated CONFIGURATION-498:
---------------------------------------
Fix Version/s: (was: 2.0)
2.x
> Add OSGi Configuration Admin Service as a source for configuration data
> -----------------------------------------------------------------------
>
> Key: CONFIGURATION-498
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-498
> Project: Commons Configuration
> Issue Type: New Feature
> Components: File reloading
> Affects Versions: 1.8
> Reporter: Brian Topping
> Fix For: 2.x
>
>
> I'm rather new to commons-configuration, so I don't have a lot of personal experience with it, so please close this issue if it is naive or poorly matched to the goals of the project. :-)
> As part of the OSGi spec, a service called "Configuration Admin" is available to provide access to properties-based configuration that is stored in the container. Providing access to that facility via commons-configuration seems like an ideal situation since it can further abstract the container that the client code is running on, now including OSGi containers such as Karaf or Felix.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)