Bug #2172
Transaction prematurely removed from workunit
Start date:
03.03.2024
Due date:
% Done:
0%
Estimated time:
origin:
Description
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.
Acceptance Criteria¶
- Nested transactions do not remove the transaction object
- Wish: Add TransactionUtil.required()/mandatory()/never() etc. mimicking the standard propagation styles.
Updated by Henning Blohm 2 days ago
- Status changed from In Progress to Resolved
This is actually the expected behavior for the user transaction.
Added tests and documentations