You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Tuomas Kiviaho (JIRA)" <ji...@apache.org> on 2014/11/14 05:58:33 UTC
[jira] [Updated] (FELIX-4694) Support binding configuration to all
registrations with the corresponding PID
[ https://issues.apache.org/jira/browse/FELIX-4694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tuomas Kiviaho updated FELIX-4694:
----------------------------------
Component/s: File Install
> Support binding configuration to all registrations with the corresponding PID
> -----------------------------------------------------------------------------
>
> Key: FELIX-4694
> URL: https://issues.apache.org/jira/browse/FELIX-4694
> Project: Felix
> Issue Type: Improvement
> Components: File Install
> Reporter: Tuomas Kiviaho
>
> Currently configurations are created without specifying bundle location so there is no way to share configuration using fileinstall. {{getConfiguration}} states that
> {code}
> * ... If the
> * location parameter is {@code null}, it will be set when a Managed Service
> * with the corresponding PID is registered for the first time. If the
> * location starts with {@code ?} then the configuration is bound to all
> * targets that are registered with the corresponding PID.
> {code}
> Now I'm forced to tweak the {{felix.cm.dir}} directly which is quite error prone approach.
> I'd be satisfied event with a global boolean flag which would enable the sharing, but I guess a more appropriate choice would be to do it per cfg.
> Another idea would be to mimic {{felix.cm.dir}} behavior so that various {{service.}} prefixed properties (not just {{service.bundleLocation}}) would be removed from the dictionary itself and be used only when communicating with {{ConfigurationAdmin}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)