Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-30689

Automation Event Handler

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Automation

      Description

      On NOS, in a multi-layer context, we'd like to be able to identify what event-handlers are contributed in a Studio project.

      For now, an event-handler is identified by an eventId and a chainId which is not enough to detect unicity as of the org.nuxeo.ecm.automation.core.events.EventHandlerRegistry is holding all contributions registered by eventId. See: org.nuxeo.ecm.automation.core.events.EventRegistry#putEventHandler.

      Ideally, we would need an eventHandlerId for identifying the atomicity of an event-handler and performing usual operations to a contribution: disable, remove, merge.

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                PagerDuty

                Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.