public class JettyRequestUpgradeStrategy extends Object implements RequestUpgradeStrategy, Lifecycle
RequestUpgradeStrategy
for use with Jetty.Constructor and Description |
---|
JettyRequestUpgradeStrategy() |
Modifier and Type | Method and Description |
---|---|
org.eclipse.jetty.websocket.api.WebSocketPolicy |
getWebSocketPolicy()
Return the configured
WebSocketPolicy , if any. |
boolean |
isRunning()
Check whether this component is currently running.
|
void |
setWebSocketPolicy(org.eclipse.jetty.websocket.api.WebSocketPolicy webSocketPolicy)
Configure a
WebSocketPolicy to use to initialize
WebSocketServerFactory . |
void |
start()
Start this component.
|
void |
stop()
Stop this component, typically in a synchronous fashion, such that the component is
fully stopped upon return of this method.
|
reactor.core.publisher.Mono<Void> |
upgrade(ServerWebExchange exchange,
WebSocketHandler handler,
String subProtocol,
Supplier<HandshakeInfo> handshakeInfoFactory)
Upgrade to a WebSocket session and handle it with the given handler.
|
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
upgrade
public void setWebSocketPolicy(org.eclipse.jetty.websocket.api.WebSocketPolicy webSocketPolicy)
WebSocketPolicy
to use to initialize
WebSocketServerFactory
.webSocketPolicy
- the WebSocket settings@Nullable public org.eclipse.jetty.websocket.api.WebSocketPolicy getWebSocketPolicy()
WebSocketPolicy
, if any.public void start()
Lifecycle
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.
start
in interface Lifecycle
SmartLifecycle.isAutoStartup()
public void stop()
Lifecycle
SmartLifecycle
and its stop(Runnable)
variant when asynchronous stop behavior is necessary.
Note that this stop notification is not guaranteed to come before destruction:
On regular shutdown, Lifecycle
beans 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.
stop
in interface Lifecycle
SmartLifecycle.stop(Runnable)
,
DisposableBean.destroy()
public boolean isRunning()
Lifecycle
In the case of a container, this will return true
only if all
components that apply are currently running.
public reactor.core.publisher.Mono<Void> upgrade(ServerWebExchange exchange, WebSocketHandler handler, @Nullable String subProtocol, Supplier<HandshakeInfo> handshakeInfoFactory)
RequestUpgradeStrategy
upgrade
in interface RequestUpgradeStrategy
exchange
- the current exchangehandler
- handler for the WebSocket sessionsubProtocol
- the selected sub-protocol got the handlerhandshakeInfoFactory
- factory to create HandshakeInfo for the WebSocket sessionMono<Void>
to indicate the outcome of the
WebSocket session handling.