Issue 771:  Question about CosTransactions behaviour (transactions)
Source:  (, )
Nature:  Uncategorized Issue
Severity:  Minor
Summary: Summary: What exception should be raised if the following Java code is executed? <find example in corresponding archive file> Resume should not raise an exception when passed a (possibly) invalid control object. However, commit must fail.

Resolution: 
Revised Text: 
Actions taken:
October 14, 1997: received issue
Discussion: 

End of Annotations:=====
Return-Path: <nagler_robert@tandem.com>
Date: Tue, 14 Oct 1997 09:16:38 -0700
From: Rob Nagler <nagler_robert@tandem.com>
To: transactions@omg.org
Subject: Question about CosTransactions behaviour

I am implementing CosTransactions v1.1 as described in orbos/97-03-04.
I have a few questions.  I apologize in advance if this isn't the
correct mailing list for such issues.

1) What exception should be raised when the following Java code is
executed?

      current.begin();
      org.omg.CosTransactions.Control control = current.suspend();
      control.get_terminator().rollback();
      current.resume(control);
      current.commit();

As I understand it, resume should not raise an exception when passed a
(possibly) invalid control object.  However, commit must fail.
Ideally,
commit should return TRANSACTION_ROLLEDBACK.  However, this would
require a history (for how long?) of all transactions in the
implementation of CosTransactions::Terminator.  My naive
implementation catches OBJECT_NOT_EXIST and raises
INVALID_TRANSACTION.  Is this sufficient?