| org.springframework.jms.connection.JmsTransactionManager
 org.springframework.jms.connection.JmsTransactionManager102
| JmsTransactionManager102 | | public class JmsTransactionManager102 extends JmsTransactionManager (Code) | | A subclass of JmsTransactionManager that uses the JMS 1.0.2 specification,
rather than the JMS 1.1 methods used by JmsTransactionManager itself.
This class can be used for JMS 1.0.2 providers, offering the same API as
JmsTransactionManager does for JMS 1.1 providers.
You need to set the pubSubDomain property accordingly, as this
class will always create either QueueConnections/QueueSessions or
TopicConnections/TopicSessions.
author:
Juergen Hoeller
since:
1.1
See Also: JmsTransactionManager102.setConnectionFactory
See Also: JmsTransactionManager102.setPubSubDomain |
| Constructor Summary | |
| public | JmsTransactionManager102()
Create a new JmsTransactionManager102 for bean-style usage. | | public | JmsTransactionManager102(ConnectionFactory connectionFactory, boolean pubSubDomain)
Create a new JmsTransactionManager102, given a ConnectionFactory. |
| Method Summary | |
| public void | afterPropertiesSet()
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()
This implementation overrides the superclass method to use JMS 1.0.2 API. | | protected Session | createSession(Connection con)
This implementation overrides the superclass method to use JMS 1.0.2 API. | | public boolean | isPubSubDomain()
Return whether the Publish/Subscribe domain (Topics) is used. | | public void | setPubSubDomain(boolean pubSubDomain)
Configure the JmsTransactionManager102 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. |
| JmsTransactionManager102 | | public JmsTransactionManager102()(Code) | | 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.
See Also: JmsTransactionManager102.setConnectionFactory |
| JmsTransactionManager102 | | public JmsTransactionManager102(ConnectionFactory connectionFactory, boolean pubSubDomain)(Code) | | Create a new JmsTransactionManager102, given a ConnectionFactory.
Parameters:
connectionFactory - the ConnectionFactory to manage transactions for
Parameters:
pubSubDomain - whether the Publish/Subscribe domain (Topics) orPoint-to-Point domain (Queues) should be used
See Also: JmsTransactionManager102.setPubSubDomain |
| afterPropertiesSet | | public void afterPropertiesSet()(Code) | | 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.
|
| createConnection | | protected Connection createConnection() throws JMSException(Code) | | This implementation overrides the superclass method to use JMS 1.0.2 API.
|
| createSession | | protected Session createSession(Connection con) throws JMSException(Code) | | This implementation overrides the superclass method to use JMS 1.0.2 API.
|
| isPubSubDomain | | public boolean isPubSubDomain()(Code) | | Return whether the Publish/Subscribe domain (Topics) is used.
Otherwise, the Point-to-Point domain (Queues) is used.
|
| setPubSubDomain | | public void setPubSubDomain(boolean pubSubDomain)(Code) | | Configure the JmsTransactionManager102 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).
Parameters:
pubSubDomain - true for Publish/Subscribe domain (Topics),false for Point-to-Point domain (Queues) |
|
|