commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Topping (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CONFIGURATION-498) Add OSGi Configuration Admin Service as a source for configuration data
Date Sun, 20 May 2012 22:17:41 GMT

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

Brian Topping updated CONFIGURATION-498:
----------------------------------------

    Issue Type: New Feature  (was: Bug)
    
> 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
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message