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

Jean-Baptiste Onofré commented on KARAF-4829:
---------------------------------------------

At some point, I wonder if it makes sense to keep both tag (for future) as it's 
exactly the same at the end:
* {{<config/>}} creates the configuration in {{ConfigAdmin}} and then the 
{{.cfg}} file
* {{<configfile/>}} create the {{.cfg}} file and the configuration in 
{{ConfigAdmin}}

So, why having two different tags ? I think it should be discussed on the dev 
mailing list.

> 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: Christian Schneider
>             Fix For: 4.0.9
>
>
> 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.4#6332)

Reply via email to