Result of nested service calls depends on presence of triggers

Issue description

A POST service S1 calls services S2 and S3. The result of this outcome depends whether a trigger is fired in S2. An exception in S3 will cause the changes of S2 to be rolled back only if S2 did not call a trigger. A trigger in S2 is currently causing an implicit commit.

Developer comments

This contradicts the requirement, that [12056, nested service call are part of the root transaction].

Rejection comment

This is acutally not the case since the package is only created upon the root service call. This means that the triggers will only be run at the very end. In this case the calls later in the sequence cannot rely on information that is augmented in a trigger. If this would be required the administrator has to explicitly call %Tobject::commit% between service calls.

Reporting date

2024-09-02

Reported by

Robert Cerny

Rejection date