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

Improve persistent manager handling

    XMLWordPrintableJSON

Details

    Description

      The current handling of persistence managers is a little bit fragile and not really deterministic.
      I propose the following enhancements:

      • Persistence managers can be registered with a "name" service property. The FilePersistenceManager gets a name, e.g. "file"
      • we add a new framework property configuration - if that's empty or not there, CM acts as today
      • if a value is configured, it's interpreted as a comma separated list of names. This list of names makes up the PMs to be used by the implementation. All of them must be registered and only these are used.
      • the PMs are used in the order they are specified in the list

      With this we have deterministic behaviour and full control while the default ootb behaviour is still maintained.

      Attachments

        1. Differentiation-between-providing-the-config-and-rem.patch
          2 kB
          Frank Hölting
        2. case2_without_felix.cm.pm.txt
          20 kB
          Frank Hölting
        3. case1_with_felix.cm.pm.txt
          39 kB
          Frank Hölting

        Activity

          People

            cziegeler Carsten Ziegeler
            cziegeler Carsten Ziegeler
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: