Jochen Walz created KARAF-6363:
----------------------------------
Summary: ConfigRepository.update changes configuration file
location
Key: KARAF-6363
URL: https://issues.apache.org/jira/browse/KARAF-6363
Project: Karaf
Issue Type: Bug
Components: karaf
Affects Versions: 4.2.6, 4.2.5, 4.2.3, 4.2.2, 4.2.1
Environment: Standard Karaf 4.2.5 installation.
Reporter: Jochen Walz
When creating a configuration for a bundle using
the ConfigRepository API and setting the felix.fileinstall.filename property to
reflect the folder where the .cfg files shall be stored, this does not have an
effect since Karaf 4.2.x any longer. It only works if the bundle already had a
configuration, since Karaf
doesn't check this property from the passed property map, but reads it from
the configuration respository. If there is not yet a configuration for this
PID, the felix.fileinstall.filename property is of course null, and then
Karaf's etc folder is prepended to the <pid>.cfg.
In Karaf 4.1.x, first the configuration was updated form the properties
passed as argument to the update function, and only then the .cfg file is
updated (using the felilx.fileinstall.filename property if this was part of
the passed properties).
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
