Knowing the number of nodes is often useful. Our internal implementation
uses a Map, so we can freely promote this to a Collection.
Change-Id: Ieaa6a9ffa32c84d8484a2ed84f027ff205c4e738
Signed-off-by: Robert Varga <rovarga@cisco.com>
import com.google.common.base.Optional;
import com.google.common.base.Preconditions;
import com.google.common.base.Predicate;
+import java.util.Collection;
import java.util.HashMap;
import java.util.Iterator;
import java.util.LinkedHashMap;
* @return all recorded direct child modifications
*/
@Override
- Iterable<ModifiedNode> getChildren() {
+ Collection<ModifiedNode> getChildren() {
return children.values();
}
import com.google.common.base.Optional;
+import java.util.Collection;
import org.opendaylight.yangtools.concepts.Identifiable;
import org.opendaylight.yangtools.yang.data.api.YangInstanceIdentifier.PathArgument;
import org.opendaylight.yangtools.yang.data.api.schema.tree.ModificationType;
/**
* Get a read-only view of children nodes.
*
- * @return Iterable of all children nodes.
+ * @return Collection of all children nodes.
*/
- abstract Iterable<? extends NodeModification> getChildren();
+ abstract Collection<? extends NodeModification> getChildren();
}