Ordering of MessageConverters in AbstractMessageBrokerConfiguration [SPR-11961] #16577
Labels
in: web
Issues in web modules (web, webmvc, webflux, websocket)
type: enhancement
A general enhancement
Milestone
Adam Granger opened SPR-11961 and commented
I wish to have a controller with like this, which returns an already-encoded JSON String.
However this is picked up by Jackson and escaped. e.g. {"foo":123} becomes {"foo":123}. Does it ever make sense to escape a single String as JSON, surely at the top level JSON can only ever start with an object or an array? See http://www.ietf.org/rfc/rfc4627.txt
The ordering is specified in AbstractMessageBrokerConfiguration#brokerMessageConverter() puts Jackson before String and ByteArray converters
I can provide my own via WebSocketMessageBrokerConfigurer, however I believe that the out-of-the-box ordering in brokerMessageConverter() should be changed to the following:
Affects: 4.0.4
Referenced from: commits 670c216
The text was updated successfully, but these errors were encountered: