public JmsTransactionManager102() 
{
	                                      	 
		super();
}

Create a new JmsTransactionManager102 for bean-style usage.

Note: The ConnectionFactory has to be set before using the instance. This constructor can be used to prepare a JmsTemplate via a BeanFactory, typically setting the ConnectionFactory via setConnectionFactory.

Also see:

setConnectionFactory

 public JmsTransactionManager102(ConnectionFactory connectionFactory,
    boolean pubSubDomain) 
{
		setConnectionFactory(connectionFactory);
		this.pubSubDomain = pubSubDomain;
		afterPropertiesSet();
}

Create a new JmsTransactionManager102, given a ConnectionFactory.

Parameters:

connectionFactory - the ConnectionFactory to manage transactions for

pubSubDomain - whether the Publish/Subscribe domain (Topics) or Point-to-Point domain (Queues) should be used

Also see:

setPubSubDomain

 public  void afterPropertiesSet() 
{
		super.afterPropertiesSet();
		// Make sure that the ConnectionFactory passed is consistent.
		// Some provider implementations of the ConnectionFactory interface
		// implement both domain interfaces under the cover, so just check if
		// the selected domain is consistent with the type of connection factory.
		if (isPubSubDomain()) {
			if (!(getConnectionFactory() instanceof TopicConnectionFactory)) {
				throw new IllegalArgumentException(
						"Specified a Spring JMS 1.0.2 transaction manager for topics " +
						"but did not supply an instance of TopicConnectionFactory");
			}
		}
		else {
			if (!(getConnectionFactory() instanceof QueueConnectionFactory)) {
				throw new IllegalArgumentException(
						"Specified a Spring JMS 1.0.2 transaction manager for queues " +
						"but did not supply an instance of QueueConnectionFactory");
			}
		}
}

In addition to checking if the connection factory is set, make sure that the supplied connection factory is of the appropriate type for the specified destination type: QueueConnectionFactory for queues, and TopicConnectionFactory for topics.

 protected Connection createConnection() throws JMSException 
{
		if (isPubSubDomain()) {
			return ((TopicConnectionFactory) getConnectionFactory()).createTopicConnection();
		}
		else {
			return ((QueueConnectionFactory) getConnectionFactory()).createQueueConnection();
		}
}

This implementation overrides the superclass method to use JMS 1.0.2 API.

 protected Session createSession(Connection con) throws JMSException 
{
		if (isPubSubDomain()) {
			return ((TopicConnection) con).createTopicSession(true, Session.AUTO_ACKNOWLEDGE);
		}
		else {
			return ((QueueConnection) con).createQueueSession(true, Session.AUTO_ACKNOWLEDGE);
		}
}

This implementation overrides the superclass method to use JMS 1.0.2 API.

 public boolean isPubSubDomain() 
{
		return this.pubSubDomain;
}

Return whether the Publish/Subscribe domain (Topics) is used. Otherwise, the Point-to-Point domain (Queues) is used.

 public  void setPubSubDomain(boolean pubSubDomain) 
{
		this.pubSubDomain = pubSubDomain;
}

Configure the transaction manager with knowledge of the JMS domain used. This tells the JMS 1.0.2 provider which class hierarchy to use for creating Connections and Sessions.

Default is Point-to-Point (Queues).