Project

General

Profile

Bug #2172

Updated by Henning Blohm 9 months ago

Currently the commit and rollback of a nested transaction removes the transaction object from the work unit. 

 It seems there is really no need to remove it but rather set the status to STATUS_NO_TRANSACTION. 

 h2. Acceptance Criteria 

 * Nested transactions do not remove the transaction object 
 * Wish: Add TransactionUtil.required()/mandatory()/never() etc. mimicking the standard propagation styles.

Back