[MGNLXAA-40] Recursive activation leaves stale content at mgnlSystem Created: 16/May/12  Updated: 22/May/12  Resolved: 18/May/12

Status: Closed
Project: Transactional Activation
Component/s: None
Affects Version/s: None
Fix Version/s: 1.2.3, 1.3.2

Type: Bug Priority: Critical
Reporter: Zdenek Skodik Assignee: Ondrej Chytil
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File magnolia-activation.log    
Issue Links:
Cloners
is cloned by MGNLXAA-44 CLONE -Recursive activation leaves st... Closed
causality
relation
is related to MGNLXAA-41 Add missing tests 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
Date of First Response:

 Description   

When you're about to activate a child, so that its parent has to be created by the receive filter explicitly, this child is removed properly when commit/rollback, however the parent stays there. It affects both the situations when you're about to activate the content for the first time, as well as if you're about to update the existing content. This can introduce inconsistencies to any next activations to the same parent tree.



 Comments   
Comment by Jan Haderka [ 17/May/12 ]

fix already in 1.2 branch

Comment by Jan Haderka [ 17/May/12 ]

Rollback() needs to use different mechanism to find original location of the file.

Comment by Jan Haderka [ 17/May/12 ]

Fixed on the branch. still need to port to trunk.

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