@Beta public final class BindingDOMTransactionChainAdapter extends Object implements BindingTransactionChain, org.opendaylight.yangtools.concepts.Delegator<DOMTransactionChain>
Constructor and Description |
---|
BindingDOMTransactionChainAdapter(DOMDataBroker chainFactory,
BindingToNormalizedNodeCodec codec,
TransactionChainListener listener) |
Modifier and Type | Method and Description |
---|---|
void |
close() |
DOMTransactionChain |
getDelegate() |
ReadTransaction |
newReadOnlyTransaction()
Allocates a new read-only transaction which provides an immutable snapshot of
the data tree.
|
AsyncReadWriteTransaction<InstanceIdentifier<?>,TreeNode> |
newReadWriteTransaction()
Allocates new read-write transaction which provides a mutable view of the data tree.
|
WriteTransaction |
newWriteOnlyTransaction()
Allocates new write-only transaction based on latest state of data tree.
|
public BindingDOMTransactionChainAdapter(DOMDataBroker chainFactory, BindingToNormalizedNodeCodec codec, TransactionChainListener listener)
public DOMTransactionChain getDelegate()
getDelegate
in interface org.opendaylight.yangtools.concepts.Delegator<DOMTransactionChain>
public ReadTransaction newReadOnlyTransaction()
AsyncDataTransactionFactory
The view of data tree is an immutable snapshot of current data tree state when transaction was allocated.
newReadOnlyTransaction
in interface BindingTransactionChain
newReadOnlyTransaction
in interface TransactionFactory
newReadOnlyTransaction
in interface AsyncDataTransactionFactory<InstanceIdentifier<?>,TreeNode>
newReadOnlyTransaction
in interface TransactionChain<InstanceIdentifier<?>,TreeNode>
public WriteTransaction newWriteOnlyTransaction()
AsyncDataTransactionFactory
Preconditions for mutation of data tree are captured from the snapshot of data tree state,
when the transaction is allocated. If data was changed during transaction in an incompatible
way then the commit of this transaction will fail. See AsyncWriteTransaction.submit()
for more details about conflicting and not-conflicting changes and failure scenarios.
Since this transaction does not provide a view of the data it SHOULD BE used only by callers
which are exclusive writers (exporters of data) to the subtree they modify. This prevents
optimistic lock failures as described in AsyncWriteTransaction.submit()
.
Exclusivity of writers to particular subtree SHOULD BE enforced by external locking mechanism.
newWriteOnlyTransaction
in interface BindingTransactionChain
newWriteOnlyTransaction
in interface TransactionFactory
newWriteOnlyTransaction
in interface AsyncDataTransactionFactory<InstanceIdentifier<?>,TreeNode>
newWriteOnlyTransaction
in interface TransactionChain<InstanceIdentifier<?>,TreeNode>
public AsyncReadWriteTransaction<InstanceIdentifier<?>,TreeNode> newReadWriteTransaction()
AsyncDataTransactionFactory
Preconditions for mutation of data tree are captured from the snapshot of data tree state, when the transaction
is allocated. If data was changed during transaction in an incompatible way then the commit of this transaction
will fail. See AsyncWriteTransaction.submit()
for more details about conflicting and not-conflicting
changes and failure scenarios.
newReadWriteTransaction
in interface AsyncDataTransactionFactory<InstanceIdentifier<?>,TreeNode>
newReadWriteTransaction
in interface TransactionChain<InstanceIdentifier<?>,TreeNode>
public void close()
close
in interface AutoCloseable
close
in interface TransactionChain<InstanceIdentifier<?>,TreeNode>
Copyright © 2019 OpenDaylight. All rights reserved.