[JMS_SPEC-92] Session.commit() etc should require TransactionInProgressException to be thrown if called in a JTA transaction Created: 29/Mar/12  Updated: 29/Mar/12

Status: Open
Project: jms-spec
Component/s: None
Affects Version/s: 1.1
Fix Version/s: None

Type: Improvement Priority: Major
Reporter: Nigel Deakin Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: pd20-veryminor

 Description   

The JMS 1.1 javadoc for TransactionInProgressException
http://docs.oracle.com/javaee/6/api/javax/jms/TransactionInProgressException.html
states:

This exception is thrown when an operation is invalid because a transaction is in progress. For instance, an attempt to call Session.commit when a session is part of a distributed transaction should throw a TransactionInProgressException.

However the javadoc for Session.commit does not list this as a mandatory exception.
http://docs.oracle.com/javaee/6/api/javax/jms/Session.html#commit%28%29

This is inconsistent.

It is hereby proposed that the definition of Session.commit and Session.rollback should be modified to require a TransactionInProgressException to be thrown when the session is in a JTA transaction.

Note that the corresponding methods on XASession already require these exceptions.

(and inconsistent with XASession.commit.


Generated at Sat Aug 29 21:00:50 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.