[
https://issues.apache.org/jira/browse/FELIX-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13131618#comment-13131618
]
Felix Meschberger commented on FELIX-3176:
------------------------------------------
Added first shot of the implementation in Rev. 1186765:
- CM_LOCATION_CHANGED event
- reassign config on location changes
- support for new configuration Regions
- Factory (internal mechanism) are not location bound any more
- Each factory configuration instance is individually bound
- adapt integration tests
- temporarily include ConfigurationEvent and ConfigurationPermission
classes from the OSGi repo for two new constants
- export cm package at version 1.4 (and reimport [1.4,1.5))
The inclusion of two OSGi Alliance classes will be reverted by FELIX-3177.
> Implement Configuration Admin 1.4 changes
> -----------------------------------------
>
> Key: FELIX-3176
> URL: https://issues.apache.org/jira/browse/FELIX-3176
> Project: Felix
> Issue Type: New Feature
> Components: Configuration Admin
> Affects Versions: configadmin-1.2.10
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: configadmin-1.4.0
>
>
> As part of the Residential Specification 4.3 the Configuration Admin Service
> will be updated to Version 1.4 with the following changes (from the spec):
> • Allow multiple bundles to register with the same PID to access to the same
> configuration, see
> Location Binding.
> • Extended Configuration Permission with a location name so that it can be
> used to prevent access
> to Configurations marked with a certain location, enabling regions, see
> Regions.
> Our implementation should be adapted to continue to serve as the RI
--
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
