Allow easier customization of MessageConverters with @EnableWebSocketMessageBroker and XML namespace [SPR-11184]

[spring-projects-issues]

Rossen Stoyanchev opened SPR-11184 and commented

WebSocketMessageBrokerConfigurer should provide a method for customizing the MessageConverter's use, for example to customize JSON message conversion.

We should also consider specifically simplifying how JSON customizations are made as that is a very likely use case.

---

Referenced from: commits 4342497

1 votes, 3 watchers

[spring-projects-issues]

Rossen Stoyanchev commented

In the mean time, with @EnableWebSocketMessageBroker setup you can:

1. remove the annotation
2. extend WebSocketMessageBrokerConfigurationSupport instead of implementing WebSocketMessageBrokerConfigurer
3. override brokerMessageConverter() method and remember to keep @Bean in the overriding method

[spring-projects-issues]

Josh Brackett commented

It looks like a 4th step for the above comment if you want to override how json is serialized/deserialized is to subclass AbstractMessageConverter yourself to provide a mechanism to provide your own ObjectMapper. The provided class MappingJackson2MessageConverter doesn't allow access to its internal ObjectMapper.

If enabling access to the ObjectMapper within the MappingJackson2MessageConverter would be a good idea should it be handled here or should I create another report?

[spring-projects-issues]

Rossen Stoyanchev commented

Yes please create a separate issue to make sure we don't forget it. Thanks.