Remove binding spec2

[mdsal.git] / binding2 / mdsal-binding2-api / src / main / java / org / opendaylight / mdsal / binding / javav2 / api / DataBroker.java

diff --git a/binding2/mdsal-binding2-api/src/main/java/org/opendaylight/mdsal/binding/javav2/api/DataBroker.java b/binding2/mdsal-binding2-api/src/main/java/org/opendaylight/mdsal/binding/javav2/api/DataBroker.java
deleted file mode 100644 (file)
index 536de55..0000000
--- a/binding2/mdsal-binding2-api/src/main/java/org/opendaylight/mdsal/binding/javav2/api/DataBroker.java
+++ /dev/null
@@ -1,53 +0,0 @@
-/*
- * Copyright (c) 2017 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.javav2.api;
-
-import com.google.common.annotations.Beta;
-
-/**
- * Provides access to a conceptual data tree store and also provides the ability to
- * subscribe for changes to data under a given branch of the tree.
- *
- * <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 ReadTransaction}, {@link WriteTransaction}
- * and {@link WriteTransaction#commit()}.
- *
- * <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.
- */
-@Beta
-public interface DataBroker extends BindingService, TransactionFactory, DataTreeService {
-    /**
-     * 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.
-     */
-    TransactionChain createTransactionChain(TransactionChainListener listener);
-}