Should the consumer accept messages while it is stopping
The JMS acknowledgement name which is one of: TRANSACTED, CLIENT_ACKNOWLEDGE, AUTO_ACKNOWLEDGE, DUPS_OK_ACKNOWLEDGE
The JMS acknowledgement mode defined as an Integer. Allows to set vendor-specific extensions to the acknowledgment mode. For the regular modes prefer to use the acknowledgementModeName instead.
If true then Camel will always make a JMS message copy of the message when it's passed to the producer for sending. Copying the message is needed in some situations such as when a replyToDestinationSelectorName is set (Camel will by the way set the alwaysCopyMessage to true if a replyToDestinationSelectorName is set)
Should the consumer container auto-startup
Sets the cache level by name for the underlying JMS resources. Possible values are:
Sets the cache level by id for the underlying JMS resources
Sets the JMS client ID to use. Note that this value if specified must be unique and can only be used by a single JMS connection instance. Its typically only required for durable topic subscriptions. You may prefer to use Virtual Topics instead
The consumer type to use, either:
Specifies the default number of concurrent consumers
The default JMS connection factory to use for the listenerConnectionFactory and templateConnectionFactory if neither are specified
Is persistent delivery used by default?
Do you want to ignore the JMSReplyTo header and so treat messages as InOnly by default and not send a reply back?
The durable subscriber name for specifying durable topic subscriptions
Enables eager loading of JMS properties as soon as a message is received which generally is inefficient as the JMS properties may not be required but sometimes can catch early any issues with the underlying JMS provider and the use of JMS properties. Can be used for testing purpose to ensure JMS properties can be understood and handled correctly.
The JMS Exception Listener used to be notified of any underlying JMS exceptions
Set if the deliveryMode, priority or timeToLive should be used when sending messages
Set if the listener session should be exposed when consuming messages
Specify the limit for idle executions of a receive task, not having received any message within its execution. If this limit is reached, the task will shut down and leave receiving to other executing tasks (in case of dynamic scheduling; see the "maxConcurrentConsumers" setting).
Allow to use your own implementation of the
The JMS connection factory used for consuming messages
Specifies the maximum number of concurrent consumers
The number of messages per task
The Spring Message Converter
When sending, should message IDs be added
Should timestamps be enabled by default on sending messages
The password which is set for the connector factory
Values of > 1 specify the message priority when sending, if the explicitQosEnabled property is specified (with 0 as the lowest priority and 9 as the highest)
Set to true if you want to send message using the QoS settings specified on the message, instead of the QoS settings on the JMS endpoint
Set whether to inhibit the delivery of messages published by its own connection
Sets the JMS Selector which is an SQL 92 predicate used to apply to messages to filter them at the message broker. You may have to encode special characters such as = as %3D
The timeout when receiving messages
The recovery interval
defines the component created temporary replyTo destination sharing strategy. Possible values are:
Provides an explicit reply to destination which overrides any incoming value of
Sets the JMS Selector using the fixed name to be used so you can filter out your own replies from the others, when using a shared queue (i.e. if you are not using a temporary reply queue).
Is persistent delivery used by default for reply?
The timeout when sending messages
@deprecated - will be removed in Camel 2.0. The JMS ServerSessionFactory if you wish to use ServerSessionFactory for consumption
Enabled by default if you specify a durableSubscriberName and a clientId
Allows you to specify a custom task executor for consuming messages
The JMS connection factory used for sending messages
Is a time to live specified when sending messages
Is transacted mode used for sending/receiving messages?
The Spring transaction manager to use
The name of the transaction to use
The timeout value of the transaction if using transacted mode
The username which is set for the connector factory
Should the old JMS API be used