You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current implementation of converters will not allow conversion of vnd types such as application/vnd.springframework.type+json, although one could set the custom types beforehand, it is useful at least on Spring Cloud Stream use cases that we could support any type that has +json on the payload.
using subtypes from MimeType would not work as json and vnd... will be consider different types.
Spring AMQP takes a different approach using just a simple contains for the word json on the content type.
It would be nice to have some sort of support on this core component and avoid another snowflake implementation on Spring Cloud Stream to override the default behavior.
Affects: 4.3.9
The text was updated successfully, but these errors were encountered:
We can add "application/*+json" as a supported MIME type, just like in the same converter for HTTP.
rstoyanchev
changed the title
Allow MappingJackson2MessageConverter to support custom vnd types [SPR-15712]
Enable support for custom vnd types in messaging MappingJackson2MessageConverter [SPR-15712]
Sep 7, 2021
Vinicius Carvalho opened SPR-15712 and commented
The current implementation of converters will not allow conversion of vnd types such as application/vnd.springframework.type+json, although one could set the custom types beforehand, it is useful at least on Spring Cloud Stream use cases that we could support any type that has +json on the payload.
using subtypes from MimeType would not work as json and vnd... will be consider different types.
Spring AMQP takes a different approach using just a simple contains for the word json on the content type.
It would be nice to have some sort of support on this core component and avoid another snowflake implementation on Spring Cloud Stream to override the default behavior.
Affects: 4.3.9
The text was updated successfully, but these errors were encountered: