I use file install (currently 3.1.10 but have also tried with 3.2.2) in
Karaf 2.2.5 to feed configurations (both normal and factory configurations)
into the config admin service.

In my configuration files I use different variables that I define in
Karaf's custom.properties file. I'm not sure whether Karaf exposes them as
system properties but they are nevertheless picked up by fileinstall.

However, when fileinstall is configured to write back configuration changes
to the configuration file, these variables are not preserved but are
expanded. This makes it very hard to read and further maintain the
configuration files. I can easily see why this is happening since the work
is divided between file install and the configuration admin and the latter
does not know about the variables at all.

I don't have a suggestion how to solve this but this is a major problem
(for me at least) to use fileinstall and config admin together. I guess if
fileinstall was just an implementation of the config admin instead of a
general listener to configuration chagnes there would be other
possibilities.

Does anyone have any suggestions how to combine write back of configuration
changes with preservation of variables? Could fileinstall provide such a
feature?

/Bengt

Reply via email to