-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The auto-config for handler classes seems not to work (manual config is required) #19
Comments
@Moongazer I have created another package wich integrates Symfony Messenger seamlessly in TYPO3. We are using it in a really big TYPO3 Application and it works quite well. I would be happy to join forces and make improvements together to bring this nice feature / component to a broader audience. |
@Moongazer The described problem here doesn´t exist in my package. It works. You can even use PHP Attributes if you are using PHP 8.1 |
@sabbelasichon Thanks for the hint! It depends a bit how fast I will be able to upgrade to v12, because than the Messenger is available as core-feature. If too many of my used extensions are not v12 ready mid of this year, I'll consider to give |
Are you sure that the Messenger Integration in the core is feature complete? |
Not sure, I think I read or heard somewhere that its not feature complete, but can't find the resource right now for details, nor the patch on Gerrit. This article says it uses a "basic implementation", whatever that means. Do you know anything more? |
I don't really know. But as far as i can see, i would consider it not feature complete out of the box. But i will have to check when we switch to version 12 |
The extension CompilerPass sets a configuration to tag
MessageHandlerInterface
classes withmessenger.message_handler
:But just implementing the interface for a custom handler class seems not be enough, the handler is never called and all messages are rejected. Only if we manually add the handler-class with this tag to our
Services.yaml
the handler is executed:Is this expected behaviour or is here missing something? Strange is, that in BOTH cases (with and without manual configuration), the tag never shows up in the cached DI file
di/DependencyInjectionContainer_4a...2a.php
: after clearing the cache, searching formessenger.message_handler
return 0 results.The text was updated successfully, but these errors were encountered: