You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Guillaume Nodet (JIRA)" <ji...@apache.org> on 2017/03/30 06:40:41 UTC

[jira] [Closed] (KARAF-4829) Make sure configFile in features makes config available early

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

Guillaume Nodet closed KARAF-4829.
----------------------------------
       Resolution: Won't Fix
    Fix Version/s:     (was: 4.2.0)

Configuration for configadmin should use the {{<config/>}} element instead.

> Make sure configFile in features makes config available early
> -------------------------------------------------------------
>
>                 Key: KARAF-4829
>                 URL: https://issues.apache.org/jira/browse/KARAF-4829
>             Project: Karaf
>          Issue Type: Improvement
>          Components: karaf-config
>    Affects Versions: 4.0.7
>            Reporter: Christian Schneider
>            Assignee: Guillaume Nodet
>
> We currently have the config and configFile elements in feature files.
> Config writes the given entries to ConfigAdmin while configFile writes a file.
> So configFile is needed if the user should get a nice file to edit. The problem with configFile is that ConfigurationAdmin reads the files asyncronously. So bundles of the feature might already be started at the time the config is written.
> So bundles might need to restart or if they only process the config once are in a kind of invalid state that does not relfect the config from the feature.
> So I propose to also write the config to ConfigAdmin if configFile is used. This should allow the bundles to come up in the correct state from the start.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)