Specifies to enable a client to use one-way or asynchronous two-way
requests when a transaction is active. Select this check box to enable transactional
messaging.
When this option is selected, the client run time will exchange SOAP request
and response messages with the server over the JMS transport in a transactional
manner if the client is operating under a transaction. This means that the
client's transaction is used to send the SOAP request message to the destination
queue or topic, and the server receives the request message only after the
client commits the transaction. Similarly, the server receives the request
message under the control of a container-managed transaction and sends the
reply message, if applicable, back to the client using that same transaction.
The client then receives the reply message only after the server's transaction
has been committed.
If this option is not selected, then the client and server run times will
perform messaging operations in a non-transactional manner as transactions
are temporarily suspended for the JMS request. The transactions are enabled
again after the request has completed.
Transactional messaging operations are not supported for two-way synchronous
operations as this leads to a deadlock condition.