Method Detail

setDestinationPrefixes

When this property is configured only messages to destinations matching
one of the configured prefixes are eligible for handling. When there is a
match the prefix is removed and only the remaining part of the destination
is used for method-mapping purposes.

By default, no prefixes are configured in which case all messages are
eligible for handling.

Destination prefixes are expected to be slash-separated Strings and
therefore a slash is automatically appended where missing to ensure a
proper prefix-based match (i.e. matching complete segments).

Note however that the remaining portion of a destination after the
prefix may use a different separator (e.g. commonly "." in messaging)
depending on the configured PathMatcher.

setMessageConverter

Configure a MessageConverter to use to convert the payload of a message from
its serialized form with a specific MIME type to an Object matching the target method
parameter. The converter is also used when sending a message to the message broker.

stop

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

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).