X-Git-Url: https://git.opendaylight.org/gerrit/gitweb?a=blobdiff_plain;f=yang%2Fyang-data-impl%2Fsrc%2Fmain%2Fjava%2Forg%2Fopendaylight%2Fyangtools%2Fyang%2Fdata%2Fimpl%2Fschema%2Ftree%2FListModificationStrategy.java;h=c8018ae90be94d9cc3438022d3ff74da05830e61;hb=bf811fae6d974d1778b6a58585fbe507d0a98b49;hp=84e2d7d490d707d074844b609d873819502b6dff;hpb=45f1165595431a54440f7b63542bb5f4ce507d5d;p=yangtools.git

diff --git a/yang/yang-data-impl/src/main/java/org/opendaylight/yangtools/yang/data/impl/schema/tree/ListModificationStrategy.java b/yang/yang-data-impl/src/main/java/org/opendaylight/yangtools/yang/data/impl/schema/tree/ListModificationStrategy.java
index 84e2d7d490..c8018ae90b 100644
--- a/yang/yang-data-impl/src/main/java/org/opendaylight/yangtools/yang/data/impl/schema/tree/ListModificationStrategy.java
+++ b/yang/yang-data-impl/src/main/java/org/opendaylight/yangtools/yang/data/impl/schema/tree/ListModificationStrategy.java
@@ -75,22 +75,20 @@ final class ListModificationStrategy extends SchemaAwareApplyOperation<ListSchem
         }
 
         /*
-         * This is where things get interesting. The user has performed a write and
-         * then she applied some more modifications to it. So we need to make sense
-         * of that an apply the operations on top of the written value. We could have
-         * done it during the write, but this operation is potentially expensive, so
-         * we have left it out of the fast path.
+         * This is where things get interesting. The user has performed a write and then she applied some more
+         * modifications to it. So we need to make sense of that an apply the operations on top of the written value. We
+         * could have done it during the write, but this operation is potentially expensive, so we have left it out of
+         * the fast path.
          *
-         * As it turns out, once we materialize the written data, we can share the
-         * code path with the subtree change. So let's create an unsealed TreeNode
-         * and run the common parts on it -- which end with the node being sealed.
+         * As it turns out, once we materialize the written data, we can share the code path with the subtree change. So
+         * let's create an unsealed TreeNode and run the common parts on it -- which end with the node being sealed.
          */
         final MutableTreeNode mutable = newValueMeta.mutable();
         mutable.setSubtreeVersion(version);
 
         @SuppressWarnings("rawtypes")
-        final NormalizedNodeContainerBuilder dataBuilder = ImmutableUnkeyedListEntryNodeBuilder
-            .create((UnkeyedListEntryNode) newValue);
+        final NormalizedNodeContainerBuilder dataBuilder =
+            ImmutableUnkeyedListEntryNodeBuilder.create((UnkeyedListEntryNode) newValue);
 
         return mutateChildren(mutable, dataBuilder, version, modification.getChildren());
     }