Remove definition deployment helper methods in IT classes to their own class

XMLWordPrintable

    • Type: Task
    • Resolution: Unresolved
    • Priority: L3 - Default
    • None
    • Affects Version/s: None
    • Component/s: backend
    • Not defined

      Context:
      Why don't we have a helper class, similar to the authorization client class, to create/deploy/run process/decision definitions? Right now, we have several abstract classes that start to copy the same code again, e.g. AbstractProcessDefinitionIT <-> AbstractFilterIT. Often one of the abstract class hierarchy doesn't fit and then we duplicate the code again in the other IT class.

      AT:

      • the code from the abstract IT classes (e.g. AbstractDefinitionIT) classes is moved to its own class similar to how it's done for the AuthorizationClient
      • all engine clients are renamed to make it clear that they are being used for the engine communication, e.g. AuthorizationEngineClient

            Assignee:
            Unassigned
            Reporter:
            Johannes
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: