[MGNLXAA-28] Session issuing the lock is not used to make changes on the content in rollback Created: 09/Dec/11  Updated: 09/Oct/12  Resolved: 05/Jan/12

Status: Closed
Project: Transactional Activation
Component/s: None
Affects Version/s: 1.2.1
Fix Version/s: 1.2.2

Type: Bug Priority: Neutral
Reporter: Jan Haderka Assignee: Milan Divilek
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by MGNLXAA-29 CLONE -Session issuing the lock is no... Closed
relation
is related to MGNLXAA-34 Add test from MGNLXAA-28 Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

In rollback we use incorrect session to perform the changes. While JR seems to be lenient to this in most cases, behavior is still not correct.



 Comments   
Comment by Jan Haderka [ 23/Dec/11 ]

And the same reason as the others ... this issue is missing a test (should be relatively easy using mockito and testing only this method while overriding all calls that are made from it). Sorry for dumping it on you.

Generated at Mon Feb 12 11:06:22 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.