Code style cleanup for prov authz and beans

[dmaap/datarouter.git] / datarouter-prov / src / main / java / org / onap / dmaap / datarouter / authz / AuthorizationResponseSupplement.java

diff --git a/datarouter-prov/src/main/java/org/onap/dmaap/datarouter/authz/AuthorizationResponseSupplement.java b/datarouter-prov/src/main/java/org/onap/dmaap/datarouter/authz/AuthorizationResponseSupplement.java
index 6e95633..2bf0d51 100644 (file)
--- a/datarouter-prov/src/main/java/org/onap/dmaap/datarouter/authz/AuthorizationResponseSupplement.java
+++ b/datarouter-prov/src/main/java/org/onap/dmaap/datarouter/authz/AuthorizationResponseSupplement.java
@@ -29,14 +29,16 @@ import java.util.Map;
 /** An object that meets the <code>AuthorizationResponseSupplement</code> interface carries supplementary\r
  * information for an authorization response.  In a XACML-based system, a response to an authorization request\r
  * carries not just the permit/deny decision but, optionally, supplemental information in the form of advice and\r
- * obligation elements.  The structure of a XACML advice element and a XACML obligation element are similar: each has an identifier and\r
- * a set of attributes (name-value) pairs.  (The difference between a XACML advice element and a XACML obligation element is in\r
+ * obligation elements.  The structure of a XACML advice element and a XACML obligation element are similar:\r
+ * each has an identifier and a set of attributes (name-value) pairs.\r
+ * (The difference between a XACML advice element and a XACML obligation element is in\r
  * how the recipient of the response--the Policy Enforcement Point, in XACML terminology--handles the element.)\r
  *\r
  * @author J. F. Lucas\r
  *\r
  */\r
 public interface AuthorizationResponseSupplement {\r
+\r
     /** Return the identifier for the supplementary information element.\r
      *\r
      * @return a <code>String</code> containing the identifier.\r