Auto-configure ObjectMapper used in the WebSocket MappingJackson2MessageConverter

I just wanted to include some cool websocket stuff within my project. This kinda worked out of the box! Thank you!!

I use SimpMessagingTemplate for sending messages. They get automatically converted to JSON, which is nice, BUT I can’t figure out which ObjectMapper is getting used for this, because it won’t use my custom Serializers and it also doesn’t use my custom Jackson settings from application.properties.

Should I just use @Autowired ObjectMapper and serialize my Objects to String by myself?

Btw: I didn’t test if it uses the correct ObjectMapper for JSON messages from the client to the server.

[benneq]

Yes, I’m using simply

@Configuration
@EnableWebSocketMessageBroker
public class WebSocketConfig extends AbstractWebSocketMessageBrokerConfigurer { ... }

I use AbstractWebSocketMessageBrokerConfigurer because I need to set the Endpoint and the Prefixes.

---

EDIT: I now use this code. Is this the right way?

@Configuration
@EnableWebSocketMessageBroker
public class WebSocketConfig extends AbstractWebSocketMessageBrokerConfigurer {
    @Autowired ObjectMapper objectMapper;

    @Override
    public void registerStompEndpoints(StompEndpointRegistry registry) {
        registry
            .addEndpoint("/stomp").withSockJS();
    }

    @Override
    public void configureMessageBroker(MessageBrokerRegistry registry) {
        registry
            .setApplicationDestinationPrefixes("/app")
            .setUserDestinationPrefix("/user")
            .enableSimpleBroker("/queue", "/topic");
    }

    @Override
    public boolean configureMessageConverters(List<MessageConverter> messageConverters) {
        DefaultContentTypeResolver resolver = new DefaultContentTypeResolver();
        resolver.setDefaultMimeType(MimeTypeUtils.APPLICATION_JSON);
        MappingJackson2MessageConverter converter = new MappingJackson2MessageConverter();
        converter.setObjectMapper(objectMapper);
        converter.setContentTypeResolver(resolver);
        messageConverters.add(converter);
        return false;
    }   
}

[joshdanhall]

I guess that might be an another approach, although as WebSocketMessageBrokerConfigurationSupport doesn’t implement WebSocketMessageBrokerConfigurer, I’m not sure how to wire it up…