Fix checkstyle violations in sal-dom-spi

[controller.git] / opendaylight / md-sal / sal-dom-spi / src / main / java / org / opendaylight / controller / sal / core / spi / data / DOMStoreTransactionChain.java

diff --git a/opendaylight/md-sal/sal-dom-spi/src/main/java/org/opendaylight/controller/sal/core/spi/data/DOMStoreTransactionChain.java b/opendaylight/md-sal/sal-dom-spi/src/main/java/org/opendaylight/controller/sal/core/spi/data/DOMStoreTransactionChain.java
index b916fddca7796e90dca402f1a8b4ac6a26fe2837..dfffd3ef401e2de1b3cd42eca99ffe4de9732345 100644 (file)
--- a/opendaylight/md-sal/sal-dom-spi/src/main/java/org/opendaylight/controller/sal/core/spi/data/DOMStoreTransactionChain.java
+++ b/opendaylight/md-sal/sal-dom-spi/src/main/java/org/opendaylight/controller/sal/core/spi/data/DOMStoreTransactionChain.java
@@ -19,10 +19,12 @@ public interface DOMStoreTransactionChain extends DOMStoreTransactionFactory, Au
      * 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.
@@ -39,10 +41,12 @@ public interface DOMStoreTransactionChain extends DOMStoreTransactionFactory, Au
      * 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.
@@ -71,6 +75,7 @@ public interface DOMStoreTransactionChain extends DOMStoreTransactionFactory, Au
     /**
      * Closes Transaction Chain.
      *
+     * <p>
      * Close method of transaction chain does not guarantee that
      * last alocated transaction is ready or was submitted.
      *