Consumer for RPC response deserializes using known type

[glenthomas]

Description

I am having problems with RPC where the responder is a java application (so no RawRabbit). The type of the response message is not returned by the responder (with a RawRabbit responder the type name would be included as a header in basicproperties.headers or in basicproperties.type). The requester does know the response type as a generic type argument, so am using that type argument for deserializing the response instead of trying to discover it from the message properties.

Check List

• [ x] All test passed.
• [ ] Added documentation (if applicable).
• [ ] Tests added to ensure functionality.
• [ x] Pull Request to stable branch.

[ChristianSauer]

Hi, any feedback on this? I stumbled on this problem, too.