JMS specification define by transactions

Question

Can JMS specification define transactions?

Answer 1

JMS specification defines a transaction tools permitting clients to send and receive groups of understandably bounded messages as one unit of information. A Session can be marked as a transacted. That means all messages sent in a session are considered as a parts of the transaction. A set of messages may be committed (commit() method) or rolled back (rollback() method). If a provider supports distributed transactions, it is recommended to use XAResource API.