Issue 652: Synchronizations in nested transactions (transactions) Source: (, ) Nature: Uncategorized Severity: Summary: Summary: What should be done if a user calls register_synchronization on a nested action Coordinator. You could raise one of the standard exceptions but some explicit text would be useful Resolution: Revised Text: Actions taken: August 5, 1997: received issue Discussion: End of Annotations:===== Return-Path: Sender: nmcl@ncl.ac.uk Date: Tue, 05 Aug 1997 15:39:19 +0100 From: Mark Little Organization: Arjuna Project To: OTS mailing list Subject: Synchronizations in nested transactions The description of the register_synchronization method of the Coordinator interface in the December 1996 spec. seems to implicitly assume that synchronizations can only be added to top-level actions. (Which makes sense if they are to be used before and after prepare, since nested actions don't undergo prepare/commit phase.) However, there is nothing in the description to say what to do if a user calls register_synchronization on a nested action Coordinator. I realise you could raise one of the standard exceptions (such as INVALID_TRANSACTION), but I was wondering whether some explicit text would be useful in the spec. as well. Mark. ----------------------------------------------------------------------- SENDER : Dr. Mark Little, Arjuna Project, Distributed Systems Research. PHONE : +44 191 222 8066, FAX : +44 191 222 8232 POST : Department of Computing Science, University of Newcastle upon Tyne, UK, NE1 7RU EMAIL : M.C.Little@newcastle.ac.uk