Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GH-1093: @RabbitListener fix abstract return type #1096

Merged
merged 1 commit into from
Sep 16, 2019

Conversation

garyrussell
Copy link
Contributor

Fixes #1093

AMQP-807 added support for generic return types; however this broke abstract
return types since the __TypeId__ header was set to the abstract type.

If the return type is not a container type and represents an abstract class
or interterface use the concrete return type to construct the JavaType.

cherry-pick to 2.1.x

Fixes spring-projects#1093

AMQP-807 added support for generic return types; however this broke abstract
return types since the `__TypeId__` header was set to the abstract type.

If the return type is not a container type and represents an abstract class
or interterface use the concrete return type to construct the `JavaType`.

**cherry-pick to 2.1.x**
@artembilan artembilan merged commit 9c1bdcd into spring-projects:master Sep 16, 2019
@garyrussell garyrussell deleted the GH-1093 branch September 16, 2019 17:40
@artembilan
Copy link
Member

... and cherry-picked into 2.1.x after fixing conflicts in test: there is no proxyBeanMethods on the @Configuration in Spring 5.1.x yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

regression possibly due to AMQP-807
2 participants