The SJMS Component is a JMS client API for use with Camel. It is based purely on the JMS API and as such does not rely on any third party messaging implementations keeping it light and flexible. It is scheduled to be released as part of Camel 2.11 with the following functionality:

The SJMS Component is a JMS client for use with Camel. SJMS uses a JMS client API written explicitly for Camel and does not depend on any third party messaging implementations keeping it light and flexible. It is scheduled to be released as part of Camel 2.11 with the following functionality:

Option	Default Value	Description
`connectionFactory`	`null`	A ConnectionFactory is required to enable the SjmsComponent. It can be set directly or set set as part of a ConnectionResource.
`connectionResource`	`null`	A ConnectionResource is an interface that allows for customization and container control of the ConnectionFactory. See Plugable Connection Resource Management for further details.
`headerFilterStrategy`	`DefaultJmsKeyFormatStrategy`
`keyFormatStrategy`	`DefaultJmsKeyFormatStrategy`
`maxConnections`	`1`	The maximum number of connections available to endpoints started under this component
`transactionCommitStrategy`	`DefaultTransactionCommitStrategy()`	Defines the number of MessageProducer instances.

Option	Default Value	Description
`connectionCount`	`1`	The maximum number of connections available to endpoints started under this component
`connectionFactory`	`null`	A ConnectionFactory is required to enable the SjmsComponent. It can be set directly or set set as part of a ConnectionResource.
`connectionResource`	`null`	A ConnectionResource is an interface that allows for customization and container control of the ConnectionFactory. See Plugable Connection Resource Management for further details.
`headerFilterStrategy`	`DefaultJmsKeyFormatStrategy`
`keyFormatStrategy`	`DefaultJmsKeyFormatStrategy`
`transactionCommitStrategy`	`null`

Usage Notes

As stated above SJMS Component uses a JMS client API that was written from the ground up for use in Camel. As such there are some key behaviors and features that deserve noting.

Plugable Connection Resource Management

SJMS provides JMS Connection resource management through built-in connection pooling. This eliminates the need to depend on third party API pooling logic. However there may be times that you are required to use an external Connection resource manager such as those provided by J2EE or OSGi containers. For this SJMS provides an interface that can be used to override the internal SJMS Connection pooling capabilities. This is accomplished through the ConnectionResource interface.

The ConnectionResource provides methods for barrowing and returning Connections as needed is the contract used to provide

pools to the SJMS component. A user should use when it is necessary to integrate SJMS with an external connection pooling manager.

It is recommended though that for standard ConnectionFactory providers you use the ConnectionFactoryResource implementation that is provided with SJMS as it is optimized for this component.

Session, Consumer, & Producer Pooling & Caching Management

Keys starting with JMS or JMSX are reserved.
exchange.in.headers keys must be literals and all be valid Java identifiers (do not use dots in the key name).
-Camel replaces dots & hyphens and the reverse when when consuming JMS messages:
-. is replaced by DOT and the reverse replacement when Camel consumes the message.