Re: Provide an option to persist a config to a file in e.g. etc

2014-01-12 Thread odb
Hi, Any follow-up on this? As far as I can tell, new configuration items are still not created in the etc/ directory (Karaf 3.0). Ivan -- View this message in context: http://apache-felix.18485.x6.nabble.com/Provide-an-option-to-persist-a-config-to-a-file-in-e-g-etc-tp4999348p5006735.html

Re: Provide an option to persist a config to a file in e.g. etc

2014-01-12 Thread Jean-Baptiste Onofré
Hi Ivan, yes, I created a Jira about that: https://issues.apache.org/jira/browse/KARAF-2656 As reminder, in previous Karaf release (Karaf 2.x), Karaf itself was responsible of the creation of files in the etc folder. Christian removed it for Karaf 3.0.0, probably he expected to delegate the

Re: Provide an option to persist a config to a file in e.g. etc

2012-09-18 Thread Christian Schneider
Hi Felix, thanks for the explanations. Do you think it is ok to add the functionality to create config files for existing config pids to fileinstall? If yes do you have any preference how to do it? I think we have the option of a special config pid property or a service API. The property

Provide an option to persist a config to a file in e.g. etc

2012-09-17 Thread Christian Schneider
Hi all, felix config admin behaves differently if the config originated from a file or was directly created in config admin. For most cases this is good. Sometimes I would like the behaviour to create a config by hand (shell or mbean) or programatically but make sure it is also created in

Re: Provide an option to persist a config to a file in e.g. etc

2012-09-17 Thread Jean-Baptiste Onofré
Hi, My preference would be to 2, more than pollute the original config with an extra attribute. My 0.02€ Regards JB On 09/17/2012 11:47 AM, Christian Schneider wrote: Hi all, felix config admin behaves differently if the config originated from a file or was directly created in config

Re: Provide an option to persist a config to a file in e.g. etc

2012-09-17 Thread Felix Meschberger
Hi Christian, Am 17.09.2012 um 11:47 schrieb Christian Schneider: Hi all, felix config admin behaves differently if the config originated from a file or was directly created in config admin. For most cases this is good. I think there is a misconception here: Configuration can always only

Re: Provide an option to persist a config to a file in e.g. etc

2012-09-17 Thread Marcel Offermans
On Sep 17, 2012, at 11:47 AM, Christian Schneider ch...@die-schneider.net wrote: felix config admin behaves differently if the config originated from a file or was directly created in config admin. For most cases this is good. Maybe I missed something, but how does the Felix implementation

Re: Provide an option to persist a config to a file in e.g. etc

2012-09-17 Thread Jean-Baptiste Onofré
I think that Christian is talking about the behavior inside Karaf where we mix FileInstall and ConfigAdmin. Regards JB On 09/17/2012 12:45 PM, Marcel Offermans wrote: On Sep 17, 2012, at 11:47 AM, Christian Schneider ch...@die-schneider.net wrote: felix config admin behaves differently if

Re: Provide an option to persist a config to a file in e.g. etc

2012-09-17 Thread Christian Schneider
Actually I am not exactly sure where which behaviour is implemented. I will dig into it though. What I can see from the outside when using felix fileinstall and config admin service together is the following: - If I have config in etc which is monitored by fileinstall then each .cfg file

Re: Provide an option to persist a config to a file in e.g. etc

2012-09-17 Thread Felix Meschberger
Hi, Am 17.09.2012 um 13:46 schrieb Christian Schneider: Actually I am not exactly sure where which behaviour is implemented. I will dig into it though. What I can see from the outside when using felix fileinstall and config admin service together is the following: - If I have config