Dear all, 

during migrating from karaf-4.3.2 to karaf-4.3.5 I recognized an strange 
behavior. 
For my bundles I've configured a configuration file via blueprint. 
Those files are provided in json format. 

When starting the karaf with an existing configuration, this file is ignored 
until it get touched. 
In version 4.3.2 and earlier, it was loaded automatically on startup. 

When providing the configuration as a cfg file, everything works fine and as 
expected. 

Can you provide my any hint, where to take a look at?

Kind regards,
Joerg

Reply via email to