JMS parameters - 8.0

If set then this string will be the prefix for all correlation ids the conduit creates and also be used in the selector for listening to replies

NON_PERSISTENT messages will kept only in memory

PERSISTENT messages will be saved to disk

Optional Client identifier for the connection. The purpose is to associate a connection with a state maintained on behalf of the client by a provider. The only such state identified by the JMS API is that required to support durable subscriptions.

Specifies the JNDI name bound to the JMS connection factory to use when connecting to the JMS destination.

Specifies the fully qualified Java class name of the "InitialContextFactory" implementation class to use.

Name of the JTA TransactionManager. Will be searched in spring, blueprint and jndi.

If a transaction manager is found then JTA transactions will be enabled. See details below.

Specifies the JNDI provider URL

Additional parameters for a JNDI provider

JMS message type used by CXF (byte, text or binary)

Password for creating the connection. Using this in the URI is discouraged

Priority for the messages. See your JMS provider documentation for details. Values range from 0 to 9 where 0 is lowest priority

Specifies the JNDI name bound to the JMS destinations where replies are sent

Timeout in milliseconds the client waits for a reply in case of request / repy exchanges

Should the transport reconnect in case of exceptions. From version 3.0.0 on the transport will always reconnect in case of exceptions

Set to true for resource local transactions. Do not set if you use JTA

Time (in ms) after which the message will be discarded by the jms provider

Reply to messages on a topic with this name. Depending on the variant this is either a jndi or jms name.

Each conduit is assigned with a UUID. If set to true this conduit id will be the prefix for all correlation ids. This allows several endpoints to share a JMS queue or topic