This repository has been archived by the owner on Dec 13, 2023. It is now read-only.
Support for binding multiple queues to the same exchanges #227
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.
Pull Request type
./gradlew generateLock saveLock
to refresh dependencies)Changes in this PR
Support for binding multiple queues to the same exchange -
Currently, Conductor support events handler to be bound to an exchange , but the problem is that the current code does not get the queue name to be bound to the exchange and it creates the queue with default name.
That means that event handlers with the same exchnage will be bound to the same queue.
In this PR, we added 'bindQueueName' param to get the queue name from the exchange uri to enable multiple event handlers to be bound to the same exchange with different queues.