You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Brian Topping (JIRA)" <ji...@apache.org> on 2012/05/21 00:15:40 UTC
[jira] [Created] (CONFIGURATION-498) Add OSGi Configuration Admin
Service as a source for configuration data
Brian Topping created CONFIGURATION-498:
-------------------------------------------
Summary: 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: Bug
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
[jira] [Commented] (CONFIGURATION-498) Add OSGi Configuration Admin
Service as a source for configuration data
Posted by "Oliver Heger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CONFIGURATION-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281837#comment-13281837 ]
Oliver Heger commented on CONFIGURATION-498:
--------------------------------------------
This is certainly a valid request. Unfortunately, I am pretty new to OSGi, so it is not directly clear for me where Commons Configuration fits into the picture.
As I have read, there are multiple aspects related to the Configuration Admin service:
* You can create a ManagedService or a ManagedServiceFactory, and then Configuration Admin calls your service when a configuration is created or changed passing in a Dictionary object. The creation of configurations is done through methods of the Configuration Admin service.
* Bundles can specify meta data describing the configuration options they support.
* There is a preferences services which can be used by bundles to persist their settings.
Which of these services would you like to access through our Configuration interface?
> 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
[jira] [Updated] (CONFIGURATION-498) Add OSGi Configuration Admin
Service as a source for configuration data
Posted by "Brian Topping (JIRA)" <ji...@apache.org>.
[ 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