Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Formatting changes to make text more friendly for PDF (Docbook).

...

JMSConfiguration options:

Name

Default

Description

connectionFactory (mandatory

Mandatory field) . Reference to a bean that defines a jms ConnectionFactory. Remember to wrap the connectionFactory like described above when not using a pooling ConnectionFactory

wrapInSingleConnectionFactory true

Will wrap the connectionFactory with a Spring SingleConnectionFactory, which can improve the performance of the jms transport. Default is true.

reconnectOnException false

If wrapping the connectionFactory with a Spring SingleConnectionFactory and reconnectOnException is true, will create a new connection if there is an exception thrown, otherwise will not try to reconnect if the there is an exception thrown. Default is false.

targetDestination

JNDI name or provider specific name of a destination. Example for ActiveMQ:
test.cxf.jmstransport.queue

replyDestination


destinationResolver

DynamicDestinationResolver

Reference to a Spring DestinationResolver. This allows to define how destination names are resolved to jms Destinations. By default a DynamicDestinationResolver is used. It resolves destinations using the jms providers features. If you reference a JndiDestinationResolver you can resolve the destination names using JNDI.

transactionManager

none

Reference to a spring transaction manager. This allows to take part in JTA Transactions with your webservice.

taskExecutor SimpleAsyncTaskExecutor

Reference to a spring TaskExecutor. This is used in listeners to decide how to handle incoming messages. Default is a spring SimpleAsyncTaskExecutor.

useJms11 > CXF 2.1.3: false

true means JMS 1.1 features are used
false means only JMS 1.0.2 features are used. Default is false.

messageIdEnabled

Default is true .

messageTimestampEnabled

Default is true .

cacheLevel -1

Specify the level of caching that the JMS listener container is allowed to apply.
Please check out the java doc of the org.springframework.jms.listenerDefaultMessageListenerContainer for more information. Default is -1.

pubSubNoLocal

false

If true, do not receive your own messages when using topics. Default is false.

receiveTimeout 0

How many milliseconds to wait for response messages. 0 (default) means wait indefinitely.

explicitQosEnabled

false

If true, means that QoS parameters are set for each message. Default is false.

deliveryMode

1

NON_PERSISTENT = 1 (default) messages will only be kept only in memory

PERSISTENT = 2    messages will be persisted to disk

priority 4

Priority for the messages. Default is 4. See your JMS provider doc for details

timeToLive 0

After this time the message will be discarded by the jms provider (default 0).

sessionTransacted

false

If true, means JMS transactions are used. (Default is false).

concurrentConsumers

1

minimum Minimum number of concurrent consumers for listener (default 1).

maxConcurrentConsumers

1

maximum Maximum number of concurrent consumers for listener (default 1).

maxConcurrentTasks

10

Maximum number of threads that handle the received requests (available from cxf 2.1.4 upwards) Default 10).

messageSelector

jms selector to filter incoming messages (allows to share a queue)

subscriptionDurable

Default false .

durableSubscriptionName

 

messageType

text (default)
text
binary
byte

pubSubDomain

false
false (default) means use queues
true means use topics

jmsProviderTibcoEms

false

true means that the jms provider is Tibco EMS. Default is false. Currently this activates that the principal in the SecurityContext is populated from the header JMS_TIBCO_SENDER. (available from cxf version 2.2.6)

useMessageIDAsCorrelationID

false

Specifies whether the If true, specifies JMS broker will use the message ID to correlate messages. By default (false) a CXF client will set a generated correlation id instead

...