Issue Bug Closed

#110223Messenger routing: wildcard fallback and ordered multi-transport route missing and leaves message bus unusable

Stefan Bürk 07/17/26, 23:53 updated 08/11/26, 08:51

Description

Scope clarification for #110223 (routing fallback + multi-transport routing)

This issue overlaps with #101699 but is not the same, and it is intentionally
kept as an additionally resolved item of the change that fixes both. The change
is filed as a bugfix (primary: #101699), while #110223 tracks the extra routing
capabilities delivered on top of the pure bug fix.

The two issues split as follows.

Covered by #101699 (the bug)

The default catch-all route '*' => 'default' was always applied in addition
to any matching specific route, so a routed message was silently sent to the
@default@ transport as well. Fixing this – a wildcard route acting as a
*fallback* that is skipped once a more specific type matched – is the bug fix.

Additionally covered by #110223 (beyond the bug)

The following was requested/implied here and is not covered by the plain
default-fanout fix of #101699:

  • Namespace-level wildcard fallback: the fallback semantics apply to a
    namespace wildcard on every level (My\Extension\Message\Import\*,
    My\Extension\Message\*, My\* …), not only to the global '*' route.
  • Routing a single message to multiple transports on purpose: a routing value
    may be given as an ordered list of transport identifiers
    (AuditableInterface::class => ['audit', 'doctrine']), preserving order.
  • Backwards-compatible single-string mapping: the legacy
    \My\Message::class => 'doctrine' syntax keeps working and is treated as the
    single-element array form.
  • Shared, side-effect-free resolution: a new
    TransportLocator::getSenderNamesForMessage() exposes the exact routing
    resolution without a message instance, and the backend
    “Configuration > Webhooks” view now shows all transports a webhook message
    is routed to (previously only a single transport was displayed).

Conclusion

Because these capabilities go beyond the default-fanout correction tracked in
#101699, #110223 remains a valid, separately scoped item. It is fully delivered
by the same change, so resolving #110223 alongside #101699 is appropriate.

To reflect that the delivered work is a behavioural correction plus the routing
capabilities above (rather than a pure feature addition), the tracker may be set
to Bug to match the resolving [BUGFIX] commit; the scope described here stays
the same either way.

Reference

  • Gerrit: change 94829 – [BUGFIX] Treat Messenger wildcard route as fallback
  • Resolves: #101699, #110223
  • Related: #107032

Reviews 4