I'm using Karaf 1.6.0 (Felix 2.0.5 I think) and File install 3.0.2. I use iPOJO (1.6.4) to create service factories that are instantiated by file install by dropping a configuration file in a dedicated directory. When I update the configuration file, file install immediately propagates, the changes to the instantiated service.
However, I can also change my configuration properties using configuration manager directly (e g via the Felix web console). When I change configuration properties this way, the properties are stored in configuration manager's bundle cache but they are not propagated back to file install and my configuration file. This means that my configuration file (used by file install) can differ from the configuration actually used and what is stored in the bundle cache. An important question regarding this is which configuration takes precedence on startup? My tests indicate that what I specify in my configuration file (which is picked up by file install) is the configuration that will be used directly after startup. I need to know whether this behavior is guaranteed (deterministic) or if this is just the way it happens to work in my case. I think I can live with either scenario - file install taking precedence or the bundle cache taking precedence - as long as the behavior is deterministic. /Bengt
