Project

General

Profile

Bug #2172

Transaction prematurely removed from workunit

Added by Henning Blohm 4 months ago. Updated 2 months ago.

Status:
Resolved
Priority:
Urgent
Assignee:
Category:
z2-base
Target version:
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.
#1

Updated by Henning Blohm 4 months ago

  • Description updated (diff)
#2

Updated by Henning Blohm 2 months ago

  • Target version changed from 2.11 to 2.10.1
#3

Updated by Henning Blohm 2 months ago

  • Status changed from In Progress to Resolved

This is actually the expected behavior for the user transaction.

Added tests and documentations

Also available in: Atom PDF