Class SubProtocolWebSocketHandler
- java.lang.Object
- org.springframework.web.socket.messaging.SubProtocolWebSocketHandler
- All Implemented Interfaces:
Lifecycle,Phased,SmartLifecycle,MessageHandler,SubProtocolCapable,WebSocketHandler
public class SubProtocolWebSocketHandler extends Object implements WebSocketHandler, SubProtocolCapable, MessageHandler, SmartLifecycle
An implementation ofWebSocketHandlerthat delegates incoming WebSocket messages to aSubProtocolHandleralong with aMessageChannelto which the sub-protocol handler can send messages from WebSocket clients to the application.Also an implementation of
MessageHandlerthat finds the WebSocket session associated with theMessageand passes it, along with the message, to the sub-protocol handler to send messages from the application back to the client.- Since:
- 4.0
- Author:
- Rossen Stoyanchev, Juergen Hoeller, Andy Wilkinson, Artem Bilan
Constructor Summary
Constructors Constructor Description SubProtocolWebSocketHandler(MessageChannel clientInboundChannel, SubscribableChannel clientOutboundChannel)Create a newSubProtocolWebSocketHandlerfor the given inbound and outbound channels.
Method Summary
All Methods Instance Methods Concrete Methods Modifier and Type Method Description voidaddProtocolHandler(SubProtocolHandler handler)Register a sub-protocol handler.voidafterConnectionClosed(WebSocketSession session, CloseStatus closeStatus)Invoked after the WebSocket connection has been closed by either side, or after a transport error has occurred.voidafterConnectionEstablished(WebSocketSession session)Invoked after WebSocket negotiation has succeeded and the WebSocket connection is opened and ready for use.protected WebSocketSessiondecorateSession(WebSocketSession session)Decorate the givenWebSocketSession, if desired.protected SubProtocolHandlerfindProtocolHandler(WebSocketSession session)Find aSubProtocolHandlerfor the given session.SubProtocolHandlergetDefaultProtocolHandler()Return the default sub-protocol handler to use.intgetPhase()Return the phase value of this object.Map<String,SubProtocolHandler>getProtocolHandlerMap()Return the sub-protocols keyed by protocol name.List<SubProtocolHandler>getProtocolHandlers()intgetSendBufferSizeLimit()Return the buffer-size limit (number of bytes).intgetSendTimeLimit()Return the send-time limit (milliseconds).StringgetStatsInfo()Return a String describing internal state and counters.List<String>getSubProtocols()Return all supported protocols.voidhandleMessage(Message<?> message)Handle an outbound Spring Message to a WebSocket client.voidhandleMessage(WebSocketSession session, WebSocketMessage<?> message)Handle an inbound message from a WebSocket client.voidhandleTransportError(WebSocketSession session, Throwable exception)Handle an error from the underlying WebSocket message transport.booleanisAutoStartup()Returnstrueif thisLifecyclecomponent should get started automatically by the container at the time that the containingApplicationContextgets refreshed.booleanisRunning()Check whether this component is currently running.voidsetDefaultProtocolHandler(SubProtocolHandler defaultProtocolHandler)Set theSubProtocolHandlerto use when the client did not request a sub-protocol.voidsetProtocolHandlers(List<SubProtocolHandler> protocolHandlers)Configure one or more handlers to use depending on the sub-protocol requested by the client in the WebSocket handshake request.voidsetSendBufferSizeLimit(int sendBufferSizeLimit)Specify the buffer-size limit (number of bytes).voidsetSendTimeLimit(int sendTimeLimit)Specify the send-time limit (milliseconds).voidstart()Start this component.voidstop()Stop this component, typically in a synchronous fashion, such that the component is fully stopped upon return of this method.voidstop(Runnable callback)Indicates that a Lifecycle component must stop if it is currently running.booleansupportsPartialMessages()Whether the WebSocketHandler handles partial messages.StringtoString()
Constructor Detail
SubProtocolWebSocketHandler
public SubProtocolWebSocketHandler(MessageChannel clientInboundChannel, SubscribableChannel clientOutboundChannel)
Create a newSubProtocolWebSocketHandlerfor the given inbound and outbound channels.- Parameters:
clientInboundChannel- the inboundMessageChannelclientOutboundChannel- the outboundMessageChannel
Method Detail
setProtocolHandlers
public void setProtocolHandlers(List<SubProtocolHandler> protocolHandlers)
Configure one or more handlers to use depending on the sub-protocol requested by the client in the WebSocket handshake request.- Parameters:
protocolHandlers- the sub-protocol handlers to use
getProtocolHandlers
public List<SubProtocolHandler> getProtocolHandlers()
addProtocolHandler
public void addProtocolHandler(SubProtocolHandler handler)
Register a sub-protocol handler.
getProtocolHandlerMap
public Map<String,SubProtocolHandler> getProtocolHandlerMap()
Return the sub-protocols keyed by protocol name.
setDefaultProtocolHandler
public void setDefaultProtocolHandler(SubProtocolHandler defaultProtocolHandler)
Set theSubProtocolHandlerto use when the client did not request a sub-protocol.- Parameters:
defaultProtocolHandler- the default handler
getDefaultProtocolHandler
public SubProtocolHandler getDefaultProtocolHandler()
Return the default sub-protocol handler to use.
getSubProtocols
public List<String> getSubProtocols()
Return all supported protocols.- Specified by:
getSubProtocolsin interfaceSubProtocolCapable
setSendTimeLimit
public void setSendTimeLimit(int sendTimeLimit)
Specify the send-time limit (milliseconds).- See Also:
ConcurrentWebSocketSessionDecorator
getSendTimeLimit
public int getSendTimeLimit()
Return the send-time limit (milliseconds).
setSendBufferSizeLimit
public void setSendBufferSizeLimit(int sendBufferSizeLimit)
Specify the buffer-size limit (number of bytes).- See Also:
ConcurrentWebSocketSessionDecorator
getSendBufferSizeLimit
public int getSendBufferSizeLimit()
Return the buffer-size limit (number of bytes).
getStatsInfo
public String getStatsInfo()
Return a String describing internal state and counters.
isAutoStartup
public boolean isAutoStartup()
Description copied from interface:SmartLifecycleReturnstrueif thisLifecyclecomponent should get started automatically by the container at the time that the containingApplicationContextgets refreshed.A value of
falseindicates that the component is intended to be started through an explicitLifecycle.start()call instead, analogous to a plainLifecycleimplementation.- Specified by:
isAutoStartupin interfaceSmartLifecycle- See Also:
Lifecycle.start(),Phased.getPhase(),LifecycleProcessor.onRefresh(),ConfigurableApplicationContext.refresh()
getPhase
public int getPhase()
Description copied from interface:PhasedReturn the phase value of this object.
start
public final void start()
Description copied from interface:LifecycleStart this component.Should not throw an exception if the component is already running.
In the case of a container, this will propagate the start signal to all components that apply.
- Specified by:
startin interfaceLifecycle- See Also:
SmartLifecycle.isAutoStartup()
stop
public final void stop()
Description copied from interface:LifecycleStop this component, typically in a synchronous fashion, such that the component is fully stopped upon return of this method. Consider implementingSmartLifecycleand itsstop(Runnable)variant when asynchronous stop behavior is necessary.Note that this stop notification is not guaranteed to come before destruction: On regular shutdown,
Lifecyclebeans will first receive a stop notification before the general destruction callbacks are being propagated; however, on hot refresh during a context's lifetime or on aborted refresh attempts, a given bean's destroy method will be called without any consideration of stop signals upfront.Should not throw an exception if the component is not running (not started yet).
In the case of a container, this will propagate the stop signal to all components that apply.
- Specified by:
stopin interfaceLifecycle- See Also:
SmartLifecycle.stop(Runnable),DisposableBean.destroy()
stop
public final void stop(Runnable callback)
Description copied from interface:SmartLifecycleIndicates that a Lifecycle component must stop if it is currently running.The provided callback is used by the
LifecycleProcessorto support an ordered, and potentially concurrent, shutdown of all components having a common shutdown order value. The callback must be executed after theSmartLifecyclecomponent does indeed stop.The
LifecycleProcessorwill call only this variant of thestopmethod; i.e.Lifecycle.stop()will not be called forSmartLifecycleimplementations unless explicitly delegated to within the implementation of this method.- Specified by:
stopin interfaceSmartLifecycle- See Also:
Lifecycle.stop(),Phased.getPhase()
isRunning
public final boolean isRunning()
Description copied from interface:LifecycleCheck whether this component is currently running.In the case of a container, this will return
trueonly if all components that apply are currently running.
afterConnectionEstablished
public void afterConnectionEstablished(WebSocketSession session) throws Exception
Description copied from interface:WebSocketHandlerInvoked after WebSocket negotiation has succeeded and the WebSocket connection is opened and ready for use.- Specified by:
afterConnectionEstablishedin interfaceWebSocketHandler- Throws:
Exception- this method can handle or propagate exceptions; see class-level Javadoc for details.
handleMessage
public void handleMessage(WebSocketSession session, WebSocketMessage<?> message) throws Exception
Handle an inbound message from a WebSocket client.- Specified by:
handleMessagein interfaceWebSocketHandler- Throws:
Exception- this method can handle or propagate exceptions; see class-level Javadoc for details.
handleMessage
public void handleMessage(Message<?> message) throws MessagingException
Handle an outbound Spring Message to a WebSocket client.- Specified by:
handleMessagein interfaceMessageHandler- Parameters:
message- the message to be handled- Throws:
MessagingException- if the handler failed to process the message
handleTransportError
public void handleTransportError(WebSocketSession session, Throwable exception) throws Exception
Description copied from interface:WebSocketHandlerHandle an error from the underlying WebSocket message transport.- Specified by:
handleTransportErrorin interfaceWebSocketHandler- Throws:
Exception- this method can handle or propagate exceptions; see class-level Javadoc for details.
afterConnectionClosed
public void afterConnectionClosed(WebSocketSession session, CloseStatus closeStatus) throws Exception
Description copied from interface:WebSocketHandlerInvoked after the WebSocket connection has been closed by either side, or after a transport error has occurred. Although the session may technically still be open, depending on the underlying implementation, sending messages at this point is discouraged and most likely will not succeed.- Specified by:
afterConnectionClosedin interfaceWebSocketHandler- Throws:
Exception- this method can handle or propagate exceptions; see class-level Javadoc for details.
supportsPartialMessages
public boolean supportsPartialMessages()
Description copied from interface:WebSocketHandlerWhether the WebSocketHandler handles partial messages. If this flag is set totrueand the underlying WebSocket server supports partial messages, then a large WebSocket message, or one of an unknown size may be split and maybe received over multiple calls toWebSocketHandler.handleMessage(WebSocketSession, WebSocketMessage). The flagWebSocketMessage.isLast()indicates if the message is partial and whether it is the last part.- Specified by:
supportsPartialMessagesin interfaceWebSocketHandler
decorateSession
protected WebSocketSession decorateSession(WebSocketSession session)
Decorate the givenWebSocketSession, if desired.The default implementation builds a
ConcurrentWebSocketSessionDecoratorwith the configuredsend-time limitandbuffer-size limit.- Parameters:
session- the originalWebSocketSession- Returns:
- the decorated
WebSocketSession, or potentially the given session as-is - Since:
- 4.3.13
findProtocolHandler
protected final SubProtocolHandler findProtocolHandler(WebSocketSession session)
Find aSubProtocolHandlerfor the given session.- Parameters:
session- theWebSocketSessionto find a handler for