karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean-Philippe CLEMENT (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KARAF-4829) Make sure configFile in features makes config available early
Date Mon, 03 Apr 2017 16:18:41 GMT

    [ https://issues.apache.org/jira/browse/KARAF-4829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15953725#comment-15953725
] 

Jean-Philippe CLEMENT commented on KARAF-4829:
----------------------------------------------

Ok good, thank you :)

> 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)

Mime
View raw message