[MGNLACTIVATION-26] ActivationCommand should ignore deleted node's children Created: 08/May/13 Updated: 21/May/13 Resolved: 13/May/13 |
|
| Status: | Closed |
| Project: | Activation |
| Component/s: | None |
| Affects Version/s: | 5.0 |
| Fix Version/s: | 5.0 |
| Type: | Task | Priority: | Neutral |
| Reporter: | Jozef Chocholacek | Assignee: | Jozef Chocholacek |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | apiteam, deletion | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoR: |
Empty
|
||||||||
| Date of First Response: | |||||||||
| Epic Link: | Same As 4.5 | ||||||||
| Sprint: | Beta 2 | ||||||||
| Description |
|
When recursively activating nodes marked as deleted, the node is first (de)activated (thus deleted) and then the command looks for its children (to act on them), which results to an InvalidItemStateException. So if the node has been already deleted, the children activation should be skipped. |
| Comments |
| Comment by Eric Hechinger [ 10/May/13 ] |
|
Use NodeTypes.Deleted.NAME.equals(nodeType.getName()) to check if a node is marked as deleted. |