maybe you can call the listener just a little bit earlier, when the kernel.response event is sent. This makes you able to catch some errors which can occur during saving data for logs.

Sending emails shouldn’t be a part of the kernel.* stuff I think. Unless you want to receive an email every time when somebody refreshes your site.

Thanks in advance for your help.

The article is very good. You could improve it by changing diagram, because is a little bit confusing. At first glance I thought that ConcreteClassFoo extends Dispatcher. Maybe sequence diagram will be more readable.

thx,
Rafal

this exactly why I made this article. I’ll try to write something similar and push to Symfony’s documentation. I must admit this part i docs can be really confusing for beginners.

for some reason I totally forgot about this issue. Thanks for the advice.

There is a small issue in your example, which could create unwanted bugs in your code when you start using advanced features of the EventDispatcher component: the dispatcher allows to stop the propagation to next listeners by calling “$event->stopPropagation()“. As you reuse the same event instance for each dispatching, stopping the propagation of the first event will also stop the propagation of the second one (meaning it will never be dispatched to listeners).
To avoid such issue, you should create a new event instance for each dispatching.