类 UserDestinationMessageHandler

构造器详细资料

• UserDestinationMessageHandler

  public UserDestinationMessageHandler​(SubscribableChannel clientInboundChannel,
                                       SubscribableChannel brokerChannel,
                                       UserDestinationResolver resolver)

  Create an instance with the given client and broker channels subscribing to handle messages from each and then sending any resolved messages to the broker channel.

  参数:

  clientInboundChannel - messages received from clients.

  brokerChannel - messages sent to the broker.

  resolver - the resolver for "user" destinations.

方法详细资料

• getUserDestinationResolver

  public UserDestinationResolver getUserDestinationResolver()

  Return the configured UserDestinationResolver.

• setBroadcastDestination

  public void setBroadcastDestination​(@Nullable
                                      String destination)

  Set a destination to broadcast messages to that remain unresolved because the user is not connected. In a multi-application server scenario this gives other application servers a chance to try.

  By default this is not set.

  参数:

  destination - the target destination.

• getBroadcastDestination

  @Nullable
  public String getBroadcastDestination()

  Return the configured destination for unresolved messages.

• getBrokerMessagingTemplate

  public MessageSendingOperations<String> getBrokerMessagingTemplate()

  Return the messaging template used to send resolved messages to the broker channel.

• setHeaderInitializer

  public void setHeaderInitializer​(@Nullable
                                   MessageHeaderInitializer headerInitializer)

  Configure a custom MessageHeaderInitializer to initialize the headers of resolved target messages.

  By default this is not set.

• getHeaderInitializer

  @Nullable
  public MessageHeaderInitializer getHeaderInitializer()

  Return the configured header initializer.

• start

  public final void start()

  从接口复制的说明: Lifecycle
  Start this component.

  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 在接口中 Lifecycle

  另请参阅:

  SmartLifecycle.isAutoStartup()

• stop

  public final void stop()

  从接口复制的说明: Lifecycle
  Stop this component, typically in a synchronous fashion, such that the component is fully stopped upon return of this method. Consider implementing 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 在接口中 Lifecycle

  另请参阅:

  SmartLifecycle.stop(Runnable), DisposableBean.destroy()

• stop

  public final void stop​(Runnable callback)

  从接口复制的说明: SmartLifecycle
  Indicates that a Lifecycle component must stop if it is currently running.

  The provided callback is used by the LifecycleProcessor to support an ordered, and potentially concurrent, shutdown of all components having a common shutdown order value. The callback must be executed after the SmartLifecycle component does indeed stop.

  The LifecycleProcessor will call only this variant of the stop method; i.e. Lifecycle.stop() will not be called for SmartLifecycle implementations unless explicitly delegated to within the implementation of this method.

  The default implementation delegates to Lifecycle.stop() and immediately triggers the given callback in the calling thread. Note that there is no synchronization between the two, so custom implementations may at least want to put the same steps within their common lifecycle monitor (if any).

  指定者:

  stop 在接口中 SmartLifecycle

  另请参阅:

  Lifecycle.stop(), SmartLifecycle.getPhase()

• isRunning

  public final boolean isRunning()

  从接口复制的说明: Lifecycle
  Check whether this component is currently running.

  In the case of a container, this will return true only if all components that apply are currently running.

  指定者:

  isRunning 在接口中 Lifecycle

  返回:

  whether the component is currently running

• handleMessage

  public void handleMessage​(Message<?> message)
                     throws MessagingException

  从接口复制的说明: MessageHandler
  Handle the given message.

  指定者:

  handleMessage 在接口中 MessageHandler

  参数:

  message - the message to be handled

  抛出:

  MessagingException - if the handler failed to process the message

• toString

  public String toString()

  覆盖:

  toString 在类中 Object