public class JettyRequestUpgradeStrategy extends java.lang.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<java.lang.Void> |
upgrade(ServerWebExchange exchange,
WebSocketHandler handler,
java.lang.String subProtocol)
Upgrade to a WebSocket session and handle it with the given handler.
|
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()
LifecycleShould 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 LifecycleSmartLifecycle.isAutoStartup()public void stop()
LifecycleSmartLifecycle
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, only destroy methods will be called.
Should not throw an exception if the component isn't started yet.
In the case of a container, this will propagate the stop signal to all components that apply.
stop in interface LifecycleSmartLifecycle.stop(Runnable),
DisposableBean.destroy()public boolean isRunning()
LifecycleIn the case of a container, this will return true only if all
components that apply are currently running.
public reactor.core.publisher.Mono<java.lang.Void> upgrade(ServerWebExchange exchange, WebSocketHandler handler, @Nullable java.lang.String subProtocol)
RequestUpgradeStrategyupgrade in interface RequestUpgradeStrategyexchange - the current exchangehandler - handler for the WebSocket sessionsubProtocol - the selected sub-protocol got the handlerMono<Void> to indicate the outcome of the
WebSocket session handling.