Extend External Task API with error event definitions

XMLWordPrintable

    • Type: Sub-task
    • Resolution: Fixed
    • Priority: L3 - Default
    • 7.15.0-alpha3, 7.15.0
    • Affects Version/s: None
    • Component/s: None
    • None

      Error trigger definitions are evaluated when externalTaskService.handleFailure and externalTaskService.complete are called.

      Before evaluating error triggers, a context switch into a process application must be performed, so that beans, etc. can be resolved (=> look up how this was decided for conditional events in case of heterogeneous clusters and with respect to async continuations on tasks)

            Assignee:
            Miklas Boskamp
            Reporter:
            Miklas Boskamp
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: