This repository has been archived by the owner on Oct 12, 2023. It is now read-only.
Newly constructed BrokeredMessage has MessageId set to null #19
Milestone
Comments
This was referenced Dec 1, 2016
|
Closing per #24 |
7 tasks
nemakam
pushed a commit
to Azure/azure-service-bus-dotnet-plugins
that referenced
this issue
Jun 8, 2017
By default, Message doesn't have its MessageId assigned. This plugin allows to register a factory to generate message IDs on all outgoing messages that do not have their message ID assigned. This completes Azure/azure-service-bus-dotnet#19 that was taken out.
SeanFeldman
pushed a commit
to SeanFeldman/azure-service-bus-dotnet
that referenced
this issue
Jul 23, 2017
* Moving Microsoft.ServiceBus.Messaging samples * Updating readme * Updating .gitignore * Adding Microsoft.Azure.ServiceBus samples * Adding Java samples * Adding readme * Readme update * Readme update
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When creating an instance of a
BrokeredMessage, theMessageIdshould be assigned a unique value.Currently, it's set to null.
This is breaking/deviating behavior from the current ASB client.
Update
After discussing this, the consensus is to allow message Id generator and a way to opt in.
The text was updated successfully, but these errors were encountered: