[
https://issues.apache.org/jira/browse/FELIX-2682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger resolved FELIX-2682.
--------------------------------------
Resolution: Won't Fix
It looks like the Configuration Admin service extensions have been dropped from
the R4.3 release in favor of bringing more substantial changes in a later
release...
Thus, I resolve this issue for now
> 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 permissions
> (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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
