Package javax.jms
Interface XATopicConnection
-
- All Superinterfaces:
Connection,TopicConnection,XAConnection
public interface XATopicConnection extends XAConnection, TopicConnection
AnXATopicConnectionprovides the same create options asTopicConnection(optional). The Topic connections created are transactional.The
XATopicConnectioninterface is optional. JMS providers are not required to support this interface. This interface is for use by JMS providers to support transactional environments. Client programs are strongly encouraged to use the transactional support available in their environment, rather than use these XA interfaces directly.- See Also:
XAConnection
-
-
Method Summary
All Methods Instance Methods Abstract Methods Modifier and Type Method Description TopicSessioncreateTopicSession(boolean transacted, int acknowledgeMode)Creates anXATopicSessionobject.XATopicSessioncreateXATopicSession()Creates anXATopicSessionobject.-
Methods inherited from interface javax.jms.Connection
close, createConnectionConsumer, getClientID, getExceptionListener, getMetaData, setClientID, setExceptionListener, start, stop
-
Methods inherited from interface javax.jms.TopicConnection
createConnectionConsumer, createDurableConnectionConsumer
-
Methods inherited from interface javax.jms.XAConnection
createSession, createXASession
-
-
-
-
Method Detail
-
createXATopicSession
XATopicSession createXATopicSession() throws JMSException
Creates anXATopicSessionobject.- Returns:
- a newly created XA topic session
- Throws:
JMSException- if theXATopicConnectionobject fails to create an XA topic session due to some internal error.
-
createTopicSession
TopicSession createTopicSession(boolean transacted, int acknowledgeMode) throws JMSException
Creates anXATopicSessionobject.- Specified by:
createTopicSessionin interfaceTopicConnection- Parameters:
transacted- usage undefinedacknowledgeMode- usage undefined- Returns:
- a newly created XA topic session
- Throws:
JMSException- if theXATopicConnectionobject fails to create an XA topic session due to some internal error.- See Also:
Session.AUTO_ACKNOWLEDGE,Session.CLIENT_ACKNOWLEDGE,Session.DUPS_OK_ACKNOWLEDGE
-
-