Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-3324

Refactoring of Import setup

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Done
    • Priority: L3 - Default
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 3.1.0
    • Component/s: backend
    • Labels:
      None
    • Epic Link:
    • PM Priority:
      10

      Description

      Context:
      The current state of the import mediator setup is quite complex. They are instantiated by a mix of injection across class hierarchy and prototype bean arguments passed to the spring beanFactory + an init method that initializes other fields calling the beanFactory.
      This has several downsides:

      • it's not easy to grasp all the dependencies while working on them (it's a collection of properties across the class hierarchy due the to complex setup
      • strict dependency on spring beanFactory
      • they are not easy to unit-test -> dependency on spring and a lot of manual mocking by internal property access required

      AT:

      • clean up the class hierarchy to use ctor parameters over injection
      • extract setup code from init methods into dedicated factoryClasses/Beans
      • consider writing unit tests to verify the behavior of major mediator classes present(timestampBased, all entities, scrollBased)
        • test backoff logic implemented in `BackoffMediator`

        mgm-controller-panel

        This is the controller panel for Smart Panels app

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                Unassigned Unassigned
                Reporter:
                sebastian.bathke Sebastian Bathke
                Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    Salesforce