felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guillaume Nodet (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (FELIX-4694) Support binding configuration to all registrations with the corresponding PID
Date Fri, 08 Sep 2017 08:16:00 GMT

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

Guillaume Nodet closed FELIX-4694.
    Resolution: Duplicate
      Assignee: Guillaume Nodet

> 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
>    Affects Versions: fileinstall-3.5.0
>            Reporter: Tuomas Kiviaho
>            Assignee: Guillaume Nodet
>         Attachments: ConfigInstaller.patch
> 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

View raw message