[MGNLXAA-44] CLONE -Recursive activation leaves stale content at mgnlSystem Created: 22/May/12 Updated: 24/May/12 Resolved: 22/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: | Milan Divilek | Assignee: | Milan Divilek |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| 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 |
|
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. |