Issue 1852: SubtransactionAwareResource (ots-rtf) Source: (, ) Nature: Uncategorized Issue Severity: Summary: Summary: if a SubtransactionAwareResource is registered with a subtransaction using register_resource then according to the current specification it is "indirectly" registered with the top-level transaction when the "subtransaction"s ancestors have completed". In the transaction systems I have knowledge of which support nested transactions, if the subtransaction or any of its parents rollback, then any resources registered would be dropped, i.e., not propagated to the parent. Resolution: Revised Text: Actions taken: August 24, 1998: received issue Discussion: End of Annotations:===== Return-Path: Date: Mon, 24 Aug 1998 12:05:57 +0100 From: Mark Little Organization: Newcastle University To: issues@omg.org, ots-rtf@omg.org Subject: further issues for OTS RTF Here are some more issues which I've come across while implementing the OTS. In no particular order: (v) if a SubtransactionAwareResource is registered with a subtransaction using register_resource then according to the current specification it is "indirectly" registered with the top-level transaction when the "subtransaction's ancestors have completed". In the transaction systems I have knowledge of which support nested transactions, if the subtransaction or any of its parents rollback, then any resources registered would be dropped, i.e., not propagated to the parent. (This is implied in the current OTS specification because the rollback_subtransaction method does not have a reference to the parent transaction as commit_subtransaction does). So, I'd recommend changing "completed" in the text to "committed". This may be what was originally meant. This also means that if register_resource is called for a subtransaction and passed a Resource then do we need to say that the Resource is not registered with the top-level transaction if the subtransaction or its parents rollback?