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

HttpMessageConverter selection as a result of @ResponseBody should consider the requested content type [SPR-5923] #10592

Closed
spring-projects-issues opened this issue Jul 12, 2009 · 0 comments
Assignees
Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) type: enhancement A general enhancement
Milestone

Comments

@spring-projects-issues
Copy link
Collaborator

Rossen Stoyanchev opened SPR-5923 and commented

Currently when a method is annotated with @ResponseBody, the AnnotationMethodHandlerAdapter loops over a list of registered HttpMessageConverters and asks each one if it supports the type of the returned value. In order to support alternating between different content types for the same resource, the AnnotationMethodHandler should take into consideration the content type requested by the client and try to find a message converter that supports both the type of the returned value as well as the client requested content type.


Affects: 3.0 M4

Referenced from: commits b11970e

@spring-projects-issues spring-projects-issues added type: enhancement A general enhancement in: web Issues in web modules (web, webmvc, webflux, websocket) labels Jan 11, 2019
@spring-projects-issues spring-projects-issues added this to the 3.0 M4 milestone Jan 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) type: enhancement A general enhancement
Projects
None yet
Development

No branches or pull requests

2 participants