Actions
Bug #101699
open
Default routing for messenger transports always applies.
Status:
New
Priority:
Should have
Assignee:
-
Category:
Miscellaneous
Target version:
-
Start date:
2023-08-16
Due date:
% Done:
0%
Estimated time:
TYPO3 Version:
12
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:
Description
When using the symfony/messenger component in TYPO3, I discovered the following limitation:
The default configuration $GLOBALS['TYPO3_CONF_VARS']['SYS']['messenger']['routing']['*'] = 'default' will apply even if a different routing target was configured for a message:
For example, if I set $GLOBALS['TYPO3_CONF_VARS']['SYS']['messenger']['routing'][OrderSavedMessage::class] = 'doctrine'; then the message will be handled twice, because the '*' => 'default' config is still a match.
I have to unset the default with unset($GLOBALS['TYPO3_CONF_VARS']['SYS']['messenger']['routing']['*']);. Unsetting the default also has no effect on the default behavior, as default .... is the default anyway.
Updated by Daniel Goerz over 1 year ago
- Related to Feature #97700: Adopt Symfony Messenger as a command bus and queue added
Actions