Class JettyWebSocketClient
- All Implemented Interfaces:
- Lifecycle,- WebSocketClient
WebSocketClient implementation for use with Jetty 12
 WebSocketClient.- Since:
- 6.2
- Author:
- Lachlan Roberts
- 
Constructor SummaryConstructorsConstructorDescriptionDefault constructor that creates and manages an instance of a JettyWebSocketClient.JettyWebSocketClient(org.eclipse.jetty.websocket.client.WebSocketClient client) Constructor that accepts an existing instance of a JettyWebSocketClient.
- 
Method SummaryModifier and TypeMethodDescriptionreactor.core.publisher.Mono<Void> execute(URI url, @Nullable HttpHeaders headers, WebSocketHandler handler) A variant ofWebSocketClient.execute(URI, WebSocketHandler)with custom headers.reactor.core.publisher.Mono<Void> execute(URI url, WebSocketHandler handler) Execute a handshake request to the given url and handle the resulting WebSocket session with the given handler.booleanCheck whether this component is currently running.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 Details- 
JettyWebSocketClientpublic JettyWebSocketClient()Default constructor that creates and manages an instance of a JettyWebSocketClient.
- 
JettyWebSocketClientpublic JettyWebSocketClient(org.eclipse.jetty.websocket.client.WebSocketClient client) Constructor that accepts an existing instance of a JettyWebSocketClient.
 
- 
- 
Method Details- 
startpublic 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 a hard start signal to all components that apply, even to non-auto-startup components. 
- 
stoppublic 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. 
- 
isRunningpublic 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.
- 
executeDescription copied from interface:WebSocketClientExecute a handshake request to the given url and handle the resulting WebSocket session with the given handler.- Specified by:
- executein interface- WebSocketClient
- Parameters:
- url- the handshake url
- handler- the handler of the WebSocket session
- Returns:
- completion Mono<Void>to indicate the outcome of the WebSocket session handling.
 
- 
executepublic reactor.core.publisher.Mono<Void> execute(URI url, @Nullable HttpHeaders headers, WebSocketHandler handler) Description copied from interface:WebSocketClientA variant ofWebSocketClient.execute(URI, WebSocketHandler)with custom headers.- Specified by:
- executein interface- WebSocketClient
- Parameters:
- url- the handshake url
- headers- custom headers for the handshake request
- handler- the handler of the WebSocket session
- Returns:
- completion Mono<Void>to indicate the outcome of the WebSocket session handling.
 
 
-