Bug 4657: Added handling of APPEARED, DISAPPEARED.

In the context of applying candidate to cursor
state APPEARED and DISPAPPEARED should be handled
same way as SUBTREE_MODIFIED.

Change-Id: I220aab3fc94fdec9cf3a158bf4c756c120d9120d
Signed-off-by: Tony Tkacik <ttkacik@cisco.com>

diff --git a/yang/yang-data-api/src/main/java/org/opendaylight/yangtools/yang/data/api/schema/tree/DataTreeCandidateNodes.java b/yang/yang-data-api/src/main/java/org/opendaylight/yangtools/yang/data/api/schema/tree/DataTreeCandidateNodes.java
index 8145bfe711884fbe1a72fba28ee7c19eb8ef1469..f6da831b3fc5b9d0f5df7e89ed1bb5f61bb73af4 100644 (file)
--- a/yang/yang-data-api/src/main/java/org/opendaylight/yangtools/yang/data/api/schema/tree/DataTreeCandidateNodes.java
+++ b/yang/yang-data-api/src/main/java/org/opendaylight/yangtools/yang/data/api/schema/tree/DataTreeCandidateNodes.java
@@ -81,6 +81,8 @@ public final class DataTreeCandidateNodes {
                 case DELETE:
                     cursor.delete(node.getIdentifier());
                     break;
+                case APPEARED:
+                case DISAPPEARED:
                 case SUBTREE_MODIFIED:
                     final Collection<DataTreeCandidateNode> children = node.getChildNodes();
                     if (!children.isEmpty()) {