Class SockJsClient
- java.lang.Object
- org.springframework.web.socket.sockjs.client.SockJsClient
- All Implemented Interfaces:
Lifecycle,WebSocketClient
public class SockJsClient extends Object implements WebSocketClient, Lifecycle
A SockJS implementation ofWebSocketClientwith fallback alternatives that simulate a WebSocket interaction through plain HTTP streaming and long polling techniques..Implements
Lifecyclein order to propagate lifecycle events to the transports it is configured with.- Since:
- 4.1
- Author:
- Rossen Stoyanchev
- See Also:
- https://github.com/sockjs/sockjs-client,
Transport
Constructor Summary
Constructors Constructor Description SockJsClient(List<Transport> transports)Create aSockJsClientwith the given transports.
Method Summary
All Methods Instance Methods Concrete Methods Modifier and Type Method Description voidclearServerInfoCache()By default the result of a SockJS "Info" request, including whether the server has WebSocket disabled and how long the request took (used for calculating transport timeout time) is cached.ListenableFuture<WebSocketSession>doHandshake(WebSocketHandler handler, String uriTemplate, Object... uriVars)ListenableFuture<WebSocketSession>doHandshake(WebSocketHandler handler, WebSocketHttpHeaders headers, URI url)String[]getHttpHeaderNames()The configured HTTP header names to be copied from the handshake headers and also included in other HTTP requests.InfoReceivergetInfoReceiver()Return the configuredInfoReceiver(nevernull).SockJsMessageCodecgetMessageCodec()Return the SockJsMessageCodec to use.protected PrincipalgetUser()Return the user to associate with the SockJS session and make available viaWebSocketSession.getPrincipal().booleanisRunning()Check whether this component is currently running.voidsetConnectTimeoutScheduler(TaskScheduler connectTimeoutScheduler)Configure aTaskSchedulerfor scheduling a connect timeout task where the timeout value is calculated based on the duration of the initial SockJS "Info" request.voidsetHttpHeaderNames(String... httpHeaderNames)The names of HTTP headers that should be copied from the handshake headers of each call todoHandshake(WebSocketHandler, WebSocketHttpHeaders, URI)and also used with other HTTP requests issued as part of that SockJS connection, e.g.voidsetInfoReceiver(InfoReceiver infoReceiver)Configure theInfoReceiverto use to perform the SockJS "Info" request before the SockJS session starts.voidsetMessageCodec(SockJsMessageCodec messageCodec)Set the SockJsMessageCodec to use.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.
Constructor Detail
SockJsClient
public SockJsClient(List<Transport> transports)
Create aSockJsClientwith the given transports.If the list includes an
XhrTransport(or more specifically an implementation ofInfoReceiver) the instance is used to initialize theinfoReceiverproperty, or otherwise is defaulted toRestTemplateXhrTransport.- Parameters:
transports- the (non-empty) list of transports to use
Method Detail
setHttpHeaderNames
public void setHttpHeaderNames(String... httpHeaderNames)
The names of HTTP headers that should be copied from the handshake headers of each call todoHandshake(WebSocketHandler, WebSocketHttpHeaders, URI)and also used with other HTTP requests issued as part of that SockJS connection, e.g. the initial info request, XHR send or receive requests.By default if this property is not set, all handshake headers are also used for other HTTP requests. Set it if you want only a subset of handshake headers (e.g. auth headers) to be used for other HTTP requests.
- Parameters:
httpHeaderNames- HTTP header names
getHttpHeaderNames
public String[] getHttpHeaderNames()
The configured HTTP header names to be copied from the handshake headers and also included in other HTTP requests.
setInfoReceiver
public void setInfoReceiver(InfoReceiver infoReceiver)
Configure theInfoReceiverto use to perform the SockJS "Info" request before the SockJS session starts.If the list of transports provided to the constructor contained an
XhrTransportor an implementation ofInfoReceiverthat instance would have been used to initialize this property, or otherwise it defaults toRestTemplateXhrTransport.- Parameters:
infoReceiver- the transport to use for the SockJS "Info" request
getInfoReceiver
public InfoReceiver getInfoReceiver()
Return the configuredInfoReceiver(nevernull).
setMessageCodec
public void setMessageCodec(SockJsMessageCodec messageCodec)
Set the SockJsMessageCodec to use.By default
Jackson2SockJsMessageCodecis used if Jackson is on the classpath.
getMessageCodec
public SockJsMessageCodec getMessageCodec()
Return the SockJsMessageCodec to use.
setConnectTimeoutScheduler
public void setConnectTimeoutScheduler(TaskScheduler connectTimeoutScheduler)
Configure aTaskSchedulerfor scheduling a connect timeout task where the timeout value is calculated based on the duration of the initial SockJS "Info" request. The connect timeout task ensures a more timely fallback but is otherwise entirely optional.By default this is not configured in which case a fallback may take longer.
- Parameters:
connectTimeoutScheduler- the task scheduler to use
start
public 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 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()
isRunning
public 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.
doHandshake
public ListenableFuture<WebSocketSession> doHandshake(WebSocketHandler handler, String uriTemplate, Object... uriVars)
- Specified by:
doHandshakein interfaceWebSocketClient
doHandshake
public final ListenableFuture<WebSocketSession> doHandshake(WebSocketHandler handler, WebSocketHttpHeaders headers, URI url)
- Specified by:
doHandshakein interfaceWebSocketClient
getUser
protected Principal getUser()
Return the user to associate with the SockJS session and make available viaWebSocketSession.getPrincipal().By default this method returns
null.- Returns:
- the user to associate with the session (possibly
null)
clearServerInfoCache
public void clearServerInfoCache()
By default the result of a SockJS "Info" request, including whether the server has WebSocket disabled and how long the request took (used for calculating transport timeout time) is cached. This method can be used to clear that cache hence causing it to re-populate.