The config/edit command changes does not takes precedence over configuration
files in the etc folder at restart
---------------------------------------------------------------------------------------------------------------
Key: FELIX-1088
URL: https://issues.apache.org/jira/browse/FELIX-1088
Project: Felix
Issue Type: Bug
Components: Karaf
Reporter: Guillaume Nodet
If you do the following
servicemix config> edit org.ops4j.pax.logging
servicemix config> log4j.appender.out.file /tmp/servicemix.log
servicemix config> update
It does create my servicemix.log file in the /tmp directory and will log stuff
there but if I shut the instance down
and restart it - it redirects back to the original location for the
servicemix.log file in the data directory.
=============
Guillaume Nodet:
Actually, this is the currently designed behavior. Configuration updates do not
take precedence over the configuration files. So each time the configuration
file is changed or reloaded due to a server restart, the changes done via the
console are lost.
However, this may be improved by saving the changes to the properties file
instead of saving the changes directly into the ConfigAdmin service.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
