Fixes Issue #1699 | CommandProcessor.Call(..) works again #1726
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.
CommandProcessor.Call(..) wasn't working because the individual gateways didn't support the generic
Subscription
only specific for that gateway. The following changes have been made:ServiceCollectionExtensions.UseExternalBus(..)
now takes in an optionalIEnumerable<Subscription>
for each reply queue type.Call(..)
the appropriate Subscription is grabbed, and theRoutingKey
andChannelName
are set to a new GUIDServiceCollectionsExtensions
to supply an Outbox when using RPCRMQRequestReply
sample to use the new changes