Allow customizing the SockJsMessageCodec in WebSocket Java config and XML namespace [SPR-12091] #16707
Labels
in: messaging
Issues in messaging modules (jms, messaging)
in: web
Issues in web modules (web, webmvc, webflux, websocket)
type: enhancement
A general enhancement
Milestone
Ben Barron opened SPR-12091 and commented
Spring Messaging (Websockets) is intended to have the ability to work without Jackson on the classpath, however it is still required to deserialize/serialize the SockJs frames because, as far as I can tell, there isn't a way to easily call
TransportHandlingSockJsService.setMessageCodec()
and provide your own implementation based on whatever serializer you wish to use.I believe the
.setMessageCodec()
method should be present on theSockJsServiceRegistration
builder which in turn would set it upon creation of theTransportHandlingSockJsService
in theSockJsServiceRegistration.createSockJsService()
method.This will allow you to do the following:
Affects: 4.0.6, 4.0.7
Reference URL: http://stackoverflow.com/questions/25349589/spring-messaging-websockets-how-to-call-setmessagecodec
Referenced from: commits 2a0765e
The text was updated successfully, but these errors were encountered: