Uploaded image for project: 'Karaf'
  1. Karaf
  2. KARAF-6363

ConfigRepository.update changes configuration file location

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 4.2.1, 4.2.2, 4.2.3, 4.2.5, 4.2.6
    • Fix Version/s: 4.3.0, 4.2.7
    • Component/s: karaf
    • Labels:
      None
    • Environment:

      Standard Karaf 4.2.5 installation.

      Description

      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).

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                jbonofre Jean-Baptiste Onofré
                Reporter:
                jochenw Jochen Walz
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: