public class Reactor2TcpStompClient extends StompClientSupport implements Lifecycle
Reactor2TcpClient.logger| Constructor and Description |
|---|
Reactor2TcpStompClient()
Create an instance with host "127.0.0.1" and port 61613.
|
Reactor2TcpStompClient(String host,
int port)
Create an instance with the given host and port to connect to
|
Reactor2TcpStompClient(TcpOperations<byte[]> tcpClient)
Create an instance with a pre-configured TCP client.
|
| Modifier and Type | Method and Description |
|---|---|
ListenableFuture<StompSession> |
connect(StompHeaders connectHeaders,
StompSessionHandler handler)
An overloaded version of
connect(StompSessionHandler) that
accepts headers to use for the STOMP CONNECT frame. |
ListenableFuture<StompSession> |
connect(StompSessionHandler handler)
Connect and notify the given
StompSessionHandler when connected
on the STOMP level. |
boolean |
isRunning()
Check whether this component is currently running.
|
void |
shutdown()
Shut down the client and release resources.
|
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.
|
createSession, getDefaultHeartbeat, getMessageConverter, getReceiptTimeLimit, getTaskScheduler, isDefaultHeartbeatEnabled, processConnectHeaders, setDefaultHeartbeat, setMessageConverter, setReceiptTimeLimit, setTaskSchedulerpublic Reactor2TcpStompClient()
public Reactor2TcpStompClient(String host, int port)
public Reactor2TcpStompClient(TcpOperations<byte[]> tcpClient)
tcpClient - the client to usepublic 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 ListenableFuture<StompSession> connect(StompSessionHandler handler)
StompSessionHandler when connected
on the STOMP level.handler - the handler for the STOMP sessionpublic ListenableFuture<StompSession> connect(StompHeaders connectHeaders, StompSessionHandler handler)
connect(StompSessionHandler) that
accepts headers to use for the STOMP CONNECT frame.connectHeaders - headers to add to the CONNECT framehandler - the handler for the STOMP sessionpublic void shutdown()