RoutableMessageBus #20
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When dispatching a message to eventBus (allowNoHandlers: true) via sync transport, SyncTransport incorrectly uses messageBus middleware instead of respecting the BusNameStamp. This causes NoHandlerForMessageException even though eventBus allows no handlers.
Make RoutableMessageBus the default autowired MessageBusInterface instead of the first registered bus. This ensures that when SyncTransport dispatches messages, it respects the BusNameStamp and routes to the correct bus with its specific middleware configuration. Changes: - Individual buses are no longer autowired for MessageBusInterface - RoutableMessageBus is now the autowired MessageBusInterface - Added fallback bus (first registered bus) for messages without BusNameStamp
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.