Top Description Methods
javax.jms

public Interface XAConnection

extends Connection
Known Direct Subinterfaces
javax.jms.XAQueueConnection, javax.jms.XATopicConnection

The XAConnection interface extends the capability of Connection by providing an XASession (optional).

The XAConnection interface 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.

Since
JMS 1.0
Version
JMS 2.0
See Also
javax.jms.XAQueueConnection, javax.jms.XATopicConnection

Method Summary

Modifier and TypeMethod and Description
public Session

Returns:

a newly created Session
createSession
(boolean
usage undefined
transacted
,
int
usage undefined
acknowledgeMode
)

Redeclares javax.jms.Connection.createSession.

Creates an Session object.
public XASession

Returns:

a newly created XASession
createXASession
()

Creates an XASession object.

Inherited from javax.jms.Connection:
closecreateConnectionConsumercreateDurableConnectionConsumercreateSessioncreateSessioncreateSharedConnectionConsumercreateSharedDurableConnectionConsumergetClientIDgetExceptionListenergetMetaDatasetClientIDsetExceptionListenerstartstop

Method Detail

createSessionback to summary
public Session createSession(boolean transacted, int acknowledgeMode) throws JMSException

Redeclares javax.jms.Connection.createSession.

Creates an Session object.

Parameters
transacted:boolean

usage undefined

acknowledgeMode:int

usage undefined

Returns:Session

a newly created Session

Exceptions
JMSException:
if the XAConnection object fails to create a Session due to some internal error.
Since
JMS 1.1
createXASessionback to summary
public XASession createXASession() throws JMSException

Creates an XASession object.

Returns:XASession

a newly created XASession

Exceptions
JMSException:
if the XAConnection object fails to create an XASession due to some internal error.
Since
JMS 1.1