public class JettyXhrTransport extends AbstractXhrTransport implements Lifecycle
HttpClient.
When used for testing purposes (e.g. load testing) the HttpClient
properties must be set to allow a larger than usual number of connections and
threads. For example:
HttpClient httpClient = new HttpClient(); httpClient.setMaxConnectionsPerDestination(1000); httpClient.setExecutor(new QueuedThreadPool(500));
logger, PRELUDE| Constructor and Description |
|---|
JettyXhrTransport(org.eclipse.jetty.client.HttpClient httpClient) |
| Modifier and Type | Method and Description |
|---|---|
protected void |
connectInternal(TransportRequest transportRequest,
WebSocketHandler handler,
URI url,
HttpHeaders handshakeHeaders,
XhrClientSockJsSession session,
SettableListenableFuture<WebSocketSession> connectFuture) |
protected ResponseEntity<String> |
executeInfoRequestInternal(URI infoUrl,
HttpHeaders headers) |
protected ResponseEntity<String> |
executeRequest(URI url,
org.eclipse.jetty.http.HttpMethod method,
HttpHeaders headers,
String body) |
ResponseEntity<String> |
executeSendRequestInternal(URI url,
HttpHeaders headers,
TextMessage message) |
org.eclipse.jetty.client.HttpClient |
getHttpClient() |
boolean |
isRunning()
Check whether this component is currently running.
|
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.
|
connect, executeInfoRequest, executeSendRequest, getRequestHeaders, getTransportTypes, isXhrStreamingDisabled, setRequestHeaders, setXhrStreamingDisabled, toStringpublic JettyXhrTransport(org.eclipse.jetty.client.HttpClient httpClient)
public org.eclipse.jetty.client.HttpClient getHttpClient()
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, 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 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.
protected void connectInternal(TransportRequest transportRequest, WebSocketHandler handler, URI url, HttpHeaders handshakeHeaders, XhrClientSockJsSession session, SettableListenableFuture<WebSocketSession> connectFuture)
connectInternal in class AbstractXhrTransportprotected ResponseEntity<String> executeInfoRequestInternal(URI infoUrl, HttpHeaders headers)
executeInfoRequestInternal in class AbstractXhrTransportpublic ResponseEntity<String> executeSendRequestInternal(URI url, HttpHeaders headers, TextMessage message)
executeSendRequestInternal in class AbstractXhrTransportprotected ResponseEntity<String> executeRequest(URI url, org.eclipse.jetty.http.HttpMethod method, HttpHeaders headers, String body)