jmikola/wildcard-event-dispatcher-bundle

Enhances the Symfony event dispatcher with support for wildcard patterns inspired by AMQP topic exchanges.

JmikolaWildcardEventDispatcherBundle

, _(*1)

This bundle integrates the WildcardEventDispatcher library with Symfony and allows event listeners to be assigned using a wildcard pattern inspired by AMQP topic exchanges., _(*2)

Symfony's event dispatcher component and the framework's existing convention for event names (dot-separated words) is already quite similar to AMQP message routing keys. This bundle is intended to be used sparingly, where wildcards may replace verbose configuration for central listeners, such as an activity logging service., _(*3)

Some background info for this bundle may be found on the symfony-devs mailing list., _(*4)

Compatibility

This bundle requires Symfony 2.3 or above., _(*5)

Configuration

There are no configuration options. Symfony will load the bundle's dependency injection extension automatically., _(*6)

The extension will create a service that composes the existing event_dispatcher service and assumes its service ID. Depending on whether debug mode is enabled, this bundle may wrap an instance of FrameworkBundle's ContainerAwareEventDispatcher or TraceableEventDispatcher class., _(*7)

Listening on Wildcard Event Patterns

This bundle enables you to use the single-word * and multi-word # wildcards when assigning event listeners. The wildcard operators are described in greater detail in the documentation for WildcardEventDispatcher., _(*8)

Single-word Wildcard

Consider the scenario where the acme.listener service is currently listening on multiple core events:, _(*9)

<service id="acme.listener" class="Acme/MainBundle/Listener">
    <tag name="kernel.listener" event="core.exception" method="onCoreEvent" />
    <tag name="kernel.listener" event="core.request" method="onCoreEvent" />
    <tag name="kernel.listener" event="core.response" method="onCoreEvent" />
</service>

You could refactor the above configuration to use the single-word * wildcard:, _(*10)

<service id="acme.listener" class="Acme/MainBundle/Listener">
    <tag name="kernel.listener" event="core.*" method="onCoreEvent" />
</service>

This listener will now observe all events starting with core. and followed by another word. An event named core would also be matched by this pattern., _(*11)

Multi-word Wildcard

Suppose there was an event in your application named core.foo.bar. The aforementioned core.* pattern would not match this event. You could use:, _(*12)

<service id="acme.listener" class="Acme/MainBundle/Listener">
    <tag name="kernel.listener" event="core.*.*" method="onCoreEvent" />
</service>

This syntax would match core.foo and core.foo.bar, but core would no longer be matched (assuming there was such an event); however, the multi-word # wildcard would allow all of these event names to be matched:, _(*13)

``` xml , <sub>(*14)</sub>

, <sub>(*15)</sub>

The `#` wildcard could also be used to listen to _all_ events in the
application:

``` xml


<service id="acme.listener" class="Acme/MainBundle/Listener">
    <tag name="kernel.listener" event="#" method="onAnyEvent" />
</service>