I'm using Karaf 2.2.5 in combination with File install 3.2.2 and have problems getting the " felix.fileinstall.enableConfigSave" work properly.
Karaf defines some (general?) file install properties in config.properties. Karaf also adds another fileinstall factory configuration for monitoring a hot deploy directory. In addition, I add a fileinstall factory configuration for monitoring an application specific directory for configurations. I put the following line in my fileinstall factory configuration: *felix.fileinstall.enableConfigSave=true* However, configuration updates are still not written back to the configuration file. Furthermore, it should not even be necessary since the documentation on the File install web site says that this is the default. The only way I can get configuration changes to be written back into the configuration file is if I edit Karaf's config.properties and add: *felix.fileinstall.enableConfigSave=true* Thus, this property is "global" in some sense and does not have the default value of true as the documentation says. I've browsed through the source code briefly and noticed that the writing back to file functionality seems to be taken care of "globally" and looks in the bundle context for a property (DirectoryWatcher.ENABLE_CONFIG_SAVE) to determine whether to write back the configuration or not. Thus this can never be specified per file install configuration. I haven't figured out where this property is set. I regard this as a bug. This setting is specified at (and should operate on) configuration basis. Shall I create a JIRA for this? /Bengt
