2 * Copyright (c) 2014 Cisco Systems, Inc. and others. All rights reserved.
4 * This program and the accompanying materials are made available under the
5 * terms of the Eclipse Public License v1.0 which accompanies this distribution,
6 * and is available at http://www.eclipse.org/legal/epl-v10.html
8 package org.opendaylight.yangtools.yang.data.api.schema.tree;
11 * Enumeration of all possible node modification states. These are used in
12 * data tree modification context to quickly assess what sort of modification
13 * the node is undergoing.
15 public enum ModificationType {
17 * Node is currently unmodified.
22 * A child node, either direct or indirect, has been modified. This means
23 * that the data representation of this node has potentially changed.
28 * This node has been placed into the tree, potentially completely replacing
29 * pre-existing contents.
34 * This node has been deleted along with any of its child nodes.
39 * This node has appeared because it is implied by one of its children. This type is usually produced when a
40 * structural container is created to host some leaf entries. It does not have an associated before-image.
42 * Its semantics is a combination of SUBTREE_MODIFIED and WRITE, depending on which context it is being interpreted.
44 * Users who track the value of the node can treat it as a WRITE. Users transforming a {@link DataTreeCandidate} to
45 * operations on a {@link DataTreeModification} should interpret it as a SUBTREE_MODIFIED and examine its children.
46 * This is needed to correctly deal with concurrent operations on the nodes children, as issuing a write on the
47 * DataTreeModification could end up removing any leaves which have not been present at the DataTree which emitted
53 * This node has disappeared because it is no longer implied by any children. This type is usually produced when a
54 * structural container is removed because it has become empty. It does not have an associated after-image.
56 * Its semantics is a combination of SUBTREE_MODIFIED and DELETE, depending on which context it is being interpreted.
57 * Users who track the value of the node can treat it as a DELETE, as the container has disappeared. Users
58 * transforming a {@link DataTreeCandidate} to operations on a {@link DataTreeModification} should interpret it as
59 * a SUBTREE_MODIFIED and examine its children.
61 * This is needed to correctly deal with concurrent operations on the nodes children, as issuing a delete on the
62 * DataTreeModification would end up removing any leaves which have not been present at the DataTree which emitted