* 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.dom.api;
-import org.opendaylight.controller.md.sal.common.api.data.AsyncDataBroker;
-import org.opendaylight.controller.md.sal.common.api.data.TransactionChainFactory;
-import org.opendaylight.controller.md.sal.common.api.data.TransactionChainListener;
-import org.opendaylight.controller.sal.core.api.BrokerService;
-import org.opendaylight.yangtools.yang.data.api.YangInstanceIdentifier;
import org.opendaylight.yangtools.yang.data.api.schema.NormalizedNode;
/**
- * Data Broker which provides data transaction and data change listener functionality
- * using {@link NormalizedNode} data format.
+ * Data Broker which provides data transaction and data change listener functionality using {@link NormalizedNode}.
+ *
+ * <p>
+ * All operations on the data tree are performed via one of the transactions:
+ * <ul>
+ * <li>Read-Only - allocated using {@link #newReadOnlyTransaction()}
+ * <li>Write-Only - allocated using {@link #newWriteOnlyTransaction()}
+ * </ul>
+ *
+ * <p>
+ * These transactions provide a stable isolated view of data tree, which is guaranteed to be not
+ * affected by other concurrent transactions, until transaction is committed.
+ *
+ * <p>
+ * For a detailed explanation of how transaction are isolated and how transaction-local changes are
+ * committed to global data tree, see {@link DOMDataTreeReadTransaction}, {@link DOMDataTreeWriteTransaction}
+ * and {@link DOMDataTreeWriteTransaction#commit()}.
*
- * This interface is type capture of generic interfaces and returns type captures
- * of results for client-code convenience.
*
+ * <p>
+ * It is strongly recommended to use the type of transaction, which provides only the minimal
+ * capabilities you need. This allows for optimizations at the data broker / data store level. For
+ * example, implementations may optimize the transaction for reading if they know ahead of time that
+ * you only need to read data - such as not keeping additional meta-data, which may be required for
+ * write transactions.
+ *
+ * <p>
+ * <b>Implementation Note:</b> This interface is not intended to be implemented by users of MD-SAL,
+ * but only to be consumed by them.
*/
-public interface DOMDataBroker extends
- AsyncDataBroker<YangInstanceIdentifier, NormalizedNode<?, ?>, DOMDataChangeListener>,
- TransactionChainFactory<YangInstanceIdentifier, NormalizedNode<?, ?>>, BrokerService, DOMExtensibleService<DOMDataBroker, DOMDataBrokerExtension> {
-
- /**
- * {@inheritDoc}
- */
- @Override
- DOMDataReadOnlyTransaction newReadOnlyTransaction();
-
- /**
- * {@inheritDoc}
- */
- @Override
- DOMDataReadWriteTransaction newReadWriteTransaction();
-
- /**
- * {@inheritDoc}
- */
- @Override
- DOMDataWriteTransaction newWriteOnlyTransaction();
-
+public interface DOMDataBroker extends DOMTransactionFactory,
+ DOMExtensibleService<DOMDataBroker, DOMDataBrokerExtension> {
/**
- * {@inheritDoc}
+ * Create a new transaction chain. The chain will be initialized to read from its backing datastore, with
+ * no outstanding transaction. Listener will be registered to handle chain-level events.
+ *
+ * @param listener Transaction chain event listener
+ * @return A new transaction chain.
*/
- @Override
- DOMTransactionChain createTransactionChain(TransactionChainListener listener);
+ DOMTransactionChain createTransactionChain(DOMTransactionChainListener listener);
}