[MGNLACTIVATION-78] Deactivation command should not be triggered on a property Created: 13/Jan/14  Updated: 14/Jan/14  Resolved: 13/Jan/14

Status: Closed
Project: Activation
Component/s: None
Affects Version/s: 5.2.1
Fix Version/s: 5.2.2

Type: Bug Priority: Blocker
Reporter: Christian Ringele Assignee: Jaroslav Simak
Resolution: Fixed Votes: 0
Labels: maintenance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Activation-Error-Property.png    
Issue Links:
causality
caused by MGNLACTIVATION-49 Deleted node is not deactivated from ... Closed
relation
is related to MGNLUI-2571 Delete action should not trigger comm... 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   

For example, assume this node structure in the config workspace:

/modules/myModule/config/someNode
/modules/myModule/config/someNode/subNode
/modules/myModule/config/someNode.property=test

If we delete /modules/myModule/config/someNode.property, deactivation is triggered and someNode is deactivated from the subscriber(s).
Now, if you try to acticvate subNode you will get an error, that parent is not yet activated (which is obvious).


Generated at Sun Feb 11 22:59:28 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.