[KARAF-4829] Make sure configFile in features makes config available early

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 4.0.7
• Component/s: karaf
• Assignee: Guillaume Nodet
• Reporter: Christian Schneider
• Created: 21/Nov/16 15:02
• Updated: 13/Sep/18 19:00
• Resolved: 30/Mar/17 06:40

Description

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.

Issue Links

• is duplicated by: KARAF-5410 Bundle loaded before cfg file
• is related to: KARAF-5074 Support for typed config files (as in Felix ConfigAdmin config files) in features
• relates to: KARAF-5082 Allow the use of external data for features configuration