Uploaded image for project: 'OpenIDM'
  1. OpenIDM
  2. OPENIDM-10120

Backport OPENIDM-8810: Scheduler objects persisted across both schedulerobjects and genericobjects repo tables

    Details

      Description

      Changes introduced by OPENIDM-6656 to use the RepositoryService when performing CRUD operations against the scheduler objects has resulted in objects being distributed across both the genericobjects and schedulerobjects tables.

      The problem is caused by the fact that our OOTB repo.jdbc.json sample configurations declare the generic scheduler object as follows:

      "scheduler" : {
          "mainTable" : "schedulerobjects",
          "propertiesTable" : "schedulerobjectproperties",
          "searchableDefault" : true
      },

      because we are now using the RepositoryService for CRUD operations, child objects below the base scheduler object type are considered generic objects and written to the genericobjects table.

      We need to change the above scheduler object definition to the following in order to include child objects:

      "scheduler/*" : {
          "mainTable" : "schedulerobjects",
          "propertiesTable" : "schedulerobjectproperties",
          "searchableDefault" : true
      },

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                mark.offutt Mark Offutt
                Reporter:
                mark.offutt Mark Offutt
                QA Assignee:
                Jakub Janoska
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: