felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Felix Meschberger (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (FELIX-2682) Implements proposed Configuration Admin Service extensions
Date Wed, 25 Sep 2013 14:06:05 GMT

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

Felix Meschberger closed FELIX-2682.

Some changes have made it into the specification and some didn't. Those that did have been
implemented in the meantime and tracked by different issues.

So this issue is to be closed.
> Implements proposed Configuration Admin Service extensions
> ----------------------------------------------------------
>                 Key: FELIX-2682
>                 URL: https://issues.apache.org/jira/browse/FELIX-2682
>             Project: Felix
>          Issue Type: Task
>          Components: Configuration Admin, Specification compliance
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
> The OSGi R4.3 Draft 2 specification contains a number of enhancements to the Configuration
Admin Service, which we should start to implement:
>    * Bundle Locations are not used and respected any more (i.e. Configuration assigned
is not restricted by location)
>    * get/setBundleLocation methods are deprecated aliases for the new get/setGroup methods
>    * Configuration assignement is now restricted by group and enforced by Java 2 security
>          (If security is not enabled, group restrictions are not enforced)
>    * new Configuration.getChangeCount() method
>    * Targetted PIDs
>    * Services may share configurations with the same PID (all services with a given PID
are provided with the configuration)
>    * Coordinator Service support
>    * more fine-grained permission model
> This issue is not about the "User Friendly Configuration" specification. This specification
is handled in a separate bundle and will most probably also end up in its own Service specification.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message