[LdapServer] Fix the SearchResultDone result code if an operation exception occurs. #63
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.
This resolves the issues brought up in this PR / bug report: #58
The issue is that we are sending the OperationException result code, during server search handler implementations, as an out of order message after the SearchResultDone is already sent. This corrects the logic so that the result code and any diagnostic message is now sent properly in the SearchResultDone message.
I will likely change the interface for handler implementations as part of the
1.0.0
release so that the newServerSearchResult
object needs to be returned by handler implementations instead of just the entries object.