/* * Copyright (c) 2018 Pantheon Technologies, s.r.o. and others. All rights reserved. * * This program and the accompanying materials are made available under the * terms of the Eclipse Public License v1.0 which accompanies this distribution, * and is available at http://www.eclipse.org/legal/epl-v10.html */ package org.opendaylight.mdsal.binding.api; import org.eclipse.jdt.annotation.NonNull; import org.opendaylight.mdsal.common.api.LogicalDatastoreType; import org.opendaylight.mdsal.common.api.TransactionDatastoreMismatchException; import org.opendaylight.yangtools.yang.binding.DataObject; import org.opendaylight.yangtools.yang.binding.InstanceIdentifier; /** * Write-like operations supported by {@link WriteTransaction} and {@link ReadWriteTransaction}. This interface defines * the operations without a tie-in with lifecycle management. */ public interface WriteOperations { /** * Stores a piece of data at the specified path. This acts as an add / replace operation, which is to say that * whole subtree will be replaced by the specified data. * *
* If you need to make sure that a parent object exists but you do not want modify its pre-existing state by using
* put, consider using {@link #merge} instead.
*
* @param store the logical data store which should be modified
* @param path the data object path
* @param data the data object to be written to the specified path
* @throws IllegalStateException if the transaction has already been submitted
* @throws NullPointerException if any of the arguments is {@code null}
* @throws TransactionDatastoreMismatchException if this transaction is already bound to a different data store
*/
* If you need to make sure that a parent object exists but you do not want modify its pre-existing state by using
* put, consider using {@link #merge} instead.
*
*
* WARNING: Using this method may introduce garbage in data store, or recreate nodes, which were deleted by
* a previous transaction. It also has a significantly higher cost than
* {@link #put(LogicalDatastoreType, InstanceIdentifier, DataObject)} and should only be used when
* absolutely necessary.
*
* @param store the logical data store which should be modified
* @param path the data object path
* @param data the data object to be written to the specified path
* @throws IllegalStateException if the transaction has already been submitted
* @throws NullPointerException if any of the arguments is {@code null}
* @throws TransactionDatastoreMismatchException if this transaction is already bound to a different data store
* @deprecated Use of this method is a manifestation of bad lifecycle management: it attempts to create data tree
* parent nodes which may have semantic meaning without assigning responsibility. The datastore handles
* all the cases which do not attach semantics, such as {@code container}s without {@code presence},
* {@code augmentation} and {@code list} encapsulation.
* This method does not work in the general case, where there are:
*
* If you require an explicit replace operation, use {@link #put} instead.
*
* @param store the logical data store which should be modified
* @param path the data object path
* @param data the data object to be merged to the specified path
* @throws IllegalStateException if the transaction has already been submitted
* @throws NullPointerException if any of the arguments is {@code null}
* @throws TransactionDatastoreMismatchException if this transaction is already bound to a different data store
*/
* If you require an explicit replace operation, use {@link #put} instead.
*
*
* WARNING: Using this method may introduce garbage in data store, or recreate nodes, which were deleted by
* a previous transaction. It is not necessary in most scenarios and has a significantly higher cost
* than {@link #merge(LogicalDatastoreType, InstanceIdentifier, DataObject)}. It should only be used
* when absolutely necessary.
*
* @param store the logical data store which should be modified
* @param path the data object path
* @param data the data object to be merged to the specified path
* @throws IllegalStateException if the transaction has already been submitted
* @throws NullPointerException if any of the arguments is {@code null}
* @throws TransactionDatastoreMismatchException if this transaction is already bound to a different data store
* @deprecated Use of this method is a manifestation of bad lifecycle management: it attempts to create data tree
* parent nodes which may have semantic meaning without assigning responsibility. The datastore handles
* all the cases which do not attach semantics, such as {@code container}s without {@code presence},
* {@code augmentation} and {@code list} encapsulation.
* This method does not work in the general case, where there are:
*
*
* Based on this analysis, all users of this method need to be migrated to have a proper lifecycle
* relationship with entities responsible for managing such semantic items which are created by this
* method.
*/
@Deprecated(since = "11.0.3")
*
* Based on this analysis, all users of this method need to be migrated to have a proper lifecycle
* relationship with entities responsible for managing such semantic items which are created by this
* method.
*/
@Deprecated(since = "11.0.3")