Uploaded image for project: 'Felix'
  1. Felix
  2. FELIX-5684

Set multi-location for created configurations

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: fileinstall-3.5.4
    • Fix Version/s: fileinstall-3.6.2
    • Component/s: File Install
    • Labels:
      None

      Description

      By default, when fileinstall creates CM configurations, they have no locations set. According to spec:

      104.4.2 Dynamic Binding:
      A null location parameter can be used to create Configuration objects that are not yet bound.
      In this case, the Configuration becomes bound to a specific location the first time that it is
      compared to a Bundle’s location.

      It is recommended that management agents explicitly set the location to a ? (a multi-location)
      to allow multiple bundles to share PIDs and not use the dynamic binding facility.

      I'd prefer "principle of least surprise", so CM configs created from etc/*.cfg files have multi-location is set by default (alternatively - we could have configuration option), so if for example there are two blueprint bundles using <cm:property-placeholder> for same PID, they can use the configuration without problems

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                gnodet Guillaume Nodet
                Reporter:
                ggrzybek Grzegorz Grzybek
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: