Uploaded image for project: 'Activation'
  1. Activation
  2. MGNLACTIVATION-78

Deactivation command should not be triggered on a property

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Blocker Blocker
    • 5.2.2
    • 5.2.1

      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).

        Acceptance criteria

          1. Activation-Error-Property.png
            Activation-Error-Property.png
            144 kB

              jsimak Jaroslav Simak
              cringele Christian Ringele
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Bug DoR
                  Task DoD