All Classes and Interfaces

Class
Description
 
Default strategy that handles dots and hyphens.
The default container which listen for messages on the JMS destination.
A default implementation of queue browsing using the Spring BrowserCallback
A default Spring ErrorHandler that logs the exception, according to configuration options.
Hints what type of default task executor our DefaultJmsMessageListenerContainer should use.
An optional interface that a JmsEndpoint may implement to return the underlying Destination object
A JMS MessageListener which can be used to delegate processing to a Camel endpoint.
This DefaultMessageListenerContainer is used for reply queues which are exclusive.
This SimpleJmsMessageListenerContainer is used for reply queues which are exclusive.
MessageSentCallback used to enrich the Camel Exchange with the actual JMSMessageID after sending to a JMS Destination using ExchangePattern.InOnly style.
A Strategy used to convert between a Camel Exchange and JmsMessage to and from a JMS Message
JMS endpoint which is browsable.
JMS component which uses Spring JMS.
Generated by camel build tools - do NOT edit this file!
 
 
JMS constants
A Consumer which uses Spring's AbstractMessageListenerContainer implementations to consume JMS messages.
Sent and receive messages to/from a JMS Queue or Topic.
Generated by camel build tools - do NOT edit this file!
Generated by camel build tools - do NOT edit this file!
 
Strategy for applying encoding and decoding of JMS headers so they apply to the JMS spec.
Represents a Message for working with JMS
Utility class for Message.
Enum for different Message types.
A JMS PollingConsumer.
 
A class which represents some metadata about the underlying JMS provider so that we can properly bridge JMS providers such as for dealing with temporary destinations.
An endpoint for a JMS Queue which is also browsable
 
JMS based SendDynamicAware which allows to optimise JMS components with the toD (dynamic to) DSL in Camel.
A JMS Endpoint for working with a TemporaryQueue
A JMS Endpoint for working with a TemporaryTopic
A strategy that allows custom components to plugin and perform custom logic when Camel creates Message instance.
Factory used to create a custom AbstractMessageListenerContainer to be used in JMS endpoints.
A creator which can build the JMS message selector query string to use with a shared reply-to queue, so we can select the correct messages we expect as replies.
Callback when a Message has been sent.
A strategy that does not do any encoding or decoding, eg.
 
ReplyHandler to handle processing replies when using regular queues.
A ReplyManager when using regular queues.
Handles a reply.
Holder which contains the Exchange and AsyncCallback to be used when the reply arrives, so we can set the reply on the Exchange and continue routing using the callback.
The ReplyManager is responsible for handling request-reply over JMS.
Base class for ReplyManager implementations.
Types for replyTo queues
This DefaultMessageListenerContainer is used for reply queues which are shared.
This SimpleJmsMessageListenerContainer is used for reply queues which are shared.
The simple container which listen for messages on the JMS destination.
 
ReplyHandler to handle processing replies when using temporary queues.
A ReplyManager when using temporary queues.
Callback to be used when using the option useMessageIDAsCorrelationID.