-
Key: OTS11-16
-
Legacy Issue Number: 3428
-
Status: open
-
Source: Versant Technology ( Craig Russell)
-
Summary:
During the afterCompletion callback, the status parameter is as if the
requester had asked for the status.What is the status for a committed transaction during afterCompletion?
And how about for a rolled back transaction?The choice among the available status values isn't obvious:
StatusCommitted - A transaction is associated with the target object
and it has completed commitment. It is likely that heuristics exists;
otherwise, the transaction would have been destroyed and
StatusNoTransaction returned.?? No heuristics should exist for the normal case, so should we assume
that afterCompletion is just after commitment and just before the
transaction is destroyed ??StatusNoTransaction - No transaction is currently associated with the
target object. This will occur after a transaction has completed.?? Then I cannot tell the difference between committed and rolled back
??StatusCommitting - A transaction is associated with the target object
and is in the process of committing. An implementation returns this
status if it has decided to commit, but has not yet completed the
process, probably because it is waiting for responses from one or
more resources.?? This sounds like the status before all resources have done commit
phase 2 ?? -
Reported: OTS 1.0b1 — Wed, 15 Mar 2000 05:00 GMT
-
Updated: Fri, 6 Mar 2015 20:57 GMT
OTS11 — OTS Synchronization afterCompletion (status)
- Key: OTS11-16
- OMG Task Force: Additional Structures for OTS RTF