element.
]]>
` with this as the bean name. It allows,
for example, access to the containers to start/stop etc, by iterating over the collection.
If the same group is used multiple times, the collection will be the aggregate of all
containers so designated.
]]>
used to receive asynchronous replies on the reply-channel the
child element is disallowed because the template itself is the listener.
A 'reply-listener' must not be provided when using Direct reply-to. See 'reply-queue'
for more information.
]]>
for replies; optional; if not supplied, methods expecting replies
will use a temporary, exclusive, auto-delete queue or, if the RabbitMQ version is 3.4 or higher,
using the 'direct reply-to' mechanism. See also 'reply-address' and 'direct-reply-to-container'.
]]>
' must be configured as a separate '' component, when only
'reply-address' is in use.
The 'reply-address' and 'reply-queue' must refer to the same queue logically for proper reply routing logic.
]]>
element). Passed to the Rabbit library when creating the connection. When not supplied, the
Rabbit library currently uses a fixed thread pool ExecutorService with 5 threads.
]]>