public class ShardedDOMTransactionChainAdapter extends Object implements DOMTransactionChain
Constructor and Description |
---|
ShardedDOMTransactionChainAdapter(Object txChainIdentifier,
DOMDataTreeService dataTreeService,
DOMTransactionChainListener txChainListener) |
Modifier and Type | Method and Description |
---|---|
void |
close() |
void |
closeReadTransaction() |
void |
closeWriteTransaction(com.google.common.util.concurrent.FluentFuture<? extends CommitInfo> commitFuture) |
DOMDataTreeReadTransaction |
newReadOnlyTransaction()
Create a new read only transaction which will continue the chain.
|
DOMDataTreeReadWriteTransaction |
newReadWriteTransaction()
Create a new read-write transaction which will continue the chain.
|
DOMDataTreeWriteTransaction |
newWriteOnlyTransaction()
Create a new write-only transaction which will continue the chain.
|
void |
transactionFailed(DOMDataTreeTransaction tx,
Throwable cause) |
public ShardedDOMTransactionChainAdapter(Object txChainIdentifier, DOMDataTreeService dataTreeService, DOMTransactionChainListener txChainListener)
public DOMDataTreeReadTransaction newReadOnlyTransaction()
DOMTransactionChain
The previous write transaction has to be either SUBMITTED (commit
was
invoked) or CANCELLED (close
was invoked).
The returned read-only transaction presents an isolated view of the data if the previous write transaction was successful - in other words, this read-only transaction will see the state changes made by the previous write transaction in the chain. However, state which was introduced by other transactions outside this transaction chain after creation of the previous transaction is not visible.
newReadOnlyTransaction
in interface DOMTransactionChain
newReadOnlyTransaction
in interface DOMTransactionFactory
public DOMDataTreeWriteTransaction newWriteOnlyTransaction()
DOMTransactionChain
The previous write transaction has to be either SUBMITTED (commit
was
invoked) or CANCELLED (close
was invoked)
The returned write-only transaction presents an isolated view of the data if the previous write transaction was successful - in other words, this write-only transaction will see the state changes made by the previous write transaction in the chain. However, state which was introduced by other transactions outside this transaction chain after creation of the previous transaction is not visible
Committing this write-only transaction using commit
will commit
the state changes in this transaction to be visible to any subsequent transaction in this chain and also to any
transaction outside this chain.
newWriteOnlyTransaction
in interface DOMTransactionChain
newWriteOnlyTransaction
in interface DOMTransactionFactory
public DOMDataTreeReadWriteTransaction newReadWriteTransaction()
DOMTransactionChain
The previous write transaction has to be either SUBMITTED (commit
was
invoked) or CANCELLED (close
was invoked).
The returned read-write transaction presents an isolated view of the data if the previous write transaction was successful - in other words, this read-write transaction will see the state changes made by the previous write transaction in the chain. However, state which was introduced by other transactions outside this transaction chain after creation of the previous transaction is not visible.
Committing this read-write transaction using commit
will commit
the state changes in this transaction to be visible to any subsequent transaction in this chain and also to any
transaction outside this chain.
newReadWriteTransaction
in interface DOMTransactionChain
newReadWriteTransaction
in interface DOMTransactionFactory
public void close()
close
in interface AutoCloseable
close
in interface org.opendaylight.yangtools.concepts.Registration
public void closeReadTransaction()
public void closeWriteTransaction(com.google.common.util.concurrent.FluentFuture<? extends CommitInfo> commitFuture)
public void transactionFailed(DOMDataTreeTransaction tx, Throwable cause)
Copyright © 2019 OpenDaylight. All rights reserved.