Helper class that simplifies JMS access code. This class requires a
JMS 1.1+ provider, because it builds on the domain-independent API.
Use the JmsTemplate102 subclass for
JMS 1.0.2 providers.
If you want to use dynamic destination creation, you must specify
the type of JMS destination to create, using the "pubSubDomain" property.
For other operations, this is not necessary, in contrast to when working
with JmsTemplate102. Point-to-Point (Queues) is the default domain.
Default settings for JMS Sessions are "not transacted" and "auto-acknowledge".
As defined by the J2EE specification, the transaction and acknowledgement
parameters are ignored when a JMS Session is created inside an active
transaction, no matter if a JTA transaction or a Spring-managed transaction.
This template uses a DynamicDestinationResolver and a SimpleMessageConverter
as default strategies for resolving a destination name or converting a message,
respectively.
If you want to use dynamic destination creation, you must specify the type of JMS destination to create, using the "pubSubDomain" property. For other operations, this is not necessary, in contrast to when working with JmsTemplate102. Point-to-Point (Queues) is the default domain.
Default settings for JMS Sessions are "not transacted" and "auto-acknowledge". As defined by the J2EE specification, the transaction and acknowledgement parameters are ignored when a JMS Session is created inside an active transaction, no matter if a JTA transaction or a Spring-managed transaction.
This template uses a DynamicDestinationResolver and a SimpleMessageConverter as default strategies for resolving a destination name or converting a message, respectively.