Issue 556:  OTS 1.1 specification changes (orb_revision)
Source:  (, )
Nature:  Uncategorized
Severity: 
Summary: Summary: OTS 1.1 spec doesn"t clearly say which module defines the TRANSACTION_REQUIRED, TRANSACTION_ROLLEDBACK, INVALID_TRANSACTION WRONG_TRANSACTION exceptions.

Resolution:  resolved close issue
Revised Text:  Add 3 lines to the end of 3.15.1 as follows: exception TRANSACTION_REQUIRED ex_body; exception TRANSACTION_ROLLEDBACK ex_body; exception INVALID_TRANSACTION ex_body. Add a new section 3.15.3, as follows: <find new section in corresponding archive file>
Actions taken:
April 28, 1997: received issue
June 20, 1997: closed issue
Discussion: 

End of Annotations:=====
Return-Path: <daemon>
Date: Fri, 25 Apr 1997 16:47:48 -0700 (PDT)
From: Alan Snyder <Alan.Snyder@Eng.Sun.COM>
Reply-To: Alan Snyder <Alan.Snyder@Eng.Sun.COM>
Subject: clarifications needed on OTS exceptions
Cc: orb_revision@omg.org
Errors-To: owner-orb_revision
Sender: owner-orb_revision
X-OMG: orb_revision
To: orb_revision

Issue 1:

The OTS 1.1 specification does not clearly say which module defines the
TRANSACTION_REQUIRED, TRANSACTION_ROLLEDBACK, INVALID_TRANSACTION, and
WRONG_TRANSACTION exceptions. The descriptions (page 10-16 and 10-17) both say
that the CosTransactions module adds these exceptions to CORBA, which is
ambiguous.

Proposed resolution: These exceptions should be defined in the CORBA module.


#556 CLOSED
Sections 3.15.1 and 3.15.3
Comment: OTS 1.1 spec doesn't clearly say which module defines the
TRANSACTION_REQUIRED, TRANSACTION_ROLLEDBACK, INVALID_TRANSACTION
WRONG_TRANSACTION exceptions.
Resolution: Add three lines to the end of 3.15.1, as follows:
	exception TRANSACTION_REQUIRED ex_body;
	exception TRANSACTION_ROLLEDBACK ex_body;
	exception INVALID_TRANSACTION ex_body;
	Add a new section 3.15.3, as follows: 
"3.15.3 Transaction exceptions
	The TRANSACTION_REQUIRED exception indicates that the request
carried a null transaction context, but an active transaction is
required.
	The TRANSACTION_ROLLEDBACK exception indicates that the
transaction associated with the request has already been rolled back
or marked to roll back.  Thus, the requested operation either could
not be performed or was not performed because further computation on
behalf of the transaction would be fruitless.
	The INVALID_TRANSACTION indicates that the request carried an
invalid transaction context.  For example, this exception could be
raised if an error occurred when trying to register a resource."