More dispatch pipeline refactoring #1929
Merged
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.
Fixed version of #1925.
This is a small follow-up to #1923. In #1923, ObjectAdapter::dispatcher() returns the dispatch pipeline, which is not quite correct when you insert your dispatcher into another object adapter.
The desired behavior is:
Connection => logger middleware associated with connection's OA => observer middleware associated with connection's OA => second OA dispatcher => second OA servant
We don't want to duplicate the logger and dispatch observer actions.
This PR fixes the code to achieve this desired behavior. I also updated the metrics test to verify it works.