services:
  # This effectively overrides Symfony's dispatcher. Tag is there to emulate what Symfony 3.4 does with its own disptacher.
  event_dispatcher:
    class: Smartbox\Integration\FrameworkBundle\Tools\EventsDeferring\EventDispatcher
    tags: ['container.hot_path']
    arguments:
      $container: '@service_container'

  smartesb.handlers.events:
      class: Smartbox\Integration\FrameworkBundle\Tools\EventsDeferring\DeferredEventsHandler
      calls:
        - [setId, ['smartesb.handlers.events']]
        - [setEventDispatcher, ['@event_dispatcher']]
        - [setFlowsVersion, ["%smartesb.flows_version%"]]

  smartesb.registry.event_filters:
    class: Smartbox\Integration\FrameworkBundle\Tools\EventsDeferring\EventFiltersRegistry

services:
  # This effectively overrides Symfony's dispatcher. Tag is there to emulate what Symfony 3.4 does with its own disptacher.
  event_dispatcher:
    class: Smartbox\Integration\FrameworkBundle\Tools\EventsDeferring\EventDispatcher
    tags:
      - { name: container.hot_path }
    arguments:
      $container: '@service_container'

  smartesb.handlers.events:
      class: Smartbox\Integration\FrameworkBundle\Tools\EventsDeferring\DeferredEventsHandler
      calls:
        - [setId, ['smartesb.handlers.events']]
        - [setEventDispatcher, ['@event_dispatcher']]
        - [setFlowsVersion, ["%smartesb.flows_version%"]]

  smartesb.registry.event_filters:
    class: Smartbox\Integration\FrameworkBundle\Tools\EventsDeferring\EventFiltersRegistry

Switch tag definition to 2.8 compatible way
SF3.4: Switch tag definition to 2.8 compatible way
