Rethrow Phase4Exception for better error handling #48
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.
I would like to propose a change to the way exceptions are handled when using the
sendMessageAndCheckForReceipt
method.The older method
sendMessage
used to throw the exception back to the calling method where it then could be logged, persisted and handled accordingly.While the newer method
sendMessageAndCheckForReceipt
also gives a general status back, it only prints the specific exception to the console which makes error handling a pain.