* sequence and each transaction must see the effects of previous transactions
* as if they happened. A chain makes no guarantees of atomicity, in fact
* transactions are committed as soon as possible.
+ *
+ * @deprecated Use {@link org.opendaylight.mdsal.dom.spi.store.DOMStoreTransactionChain} instead.
*/
+@Deprecated
public interface DOMStoreTransactionChain extends DOMStoreTransactionFactory, AutoCloseable {
/**
* Create a new read only transaction which will continue the chain. The
* previous write transaction has to be either READY or CANCELLED.
*
+ * <p>
* If previous write transaction was already commited to data store, new
* read-only transaction is same as obtained via {@link DOMStore#newReadOnlyTransaction()}
* and contains merged result of previous one and current state of data store.
*
+ * <p>
* Otherwise read-only transaction presents isolated view as if previous read-write
* transaction was successful. State which was introduced by other transactions
* outside this transaction chain after creation of previous transaction is not visible.
* Create a new read write transaction which will continue the chain. The
* previous read-write transaction has to be either COMMITED or CANCELLED.
*
+ * <p>
* If previous write transaction was already commited to data store, new
* read-write transaction is same as obtained via {@link DOMStore#newReadWriteTransaction()}
* and contains merged result of previous one and current state of data store.
*
+ * <p>
* Otherwise read-write transaction presents isolated view as if previous read-write
* transaction was successful. State which was introduced by other transactions
* outside this transaction chain after creation of previous transaction is not visible.
/**
* Closes Transaction Chain.
*
+ * <p>
* Close method of transaction chain does not guarantee that
* last alocated transaction is ready or was submitted.
*