summaryrefslogtreecommitdiffstats
path: root/models-interactions/model-impl/cds/src
diff options
context:
space:
mode:
Diffstat (limited to 'models-interactions/model-impl/cds/src')
-rw-r--r--models-interactions/model-impl/cds/src/main/java/org/onap/policy/cds/CdsResponse.java1
-rw-r--r--models-interactions/model-impl/cds/src/main/java/org/onap/policy/cds/api/CdsProcessorListener.java13
2 files changed, 8 insertions, 6 deletions
diff --git a/models-interactions/model-impl/cds/src/main/java/org/onap/policy/cds/CdsResponse.java b/models-interactions/model-impl/cds/src/main/java/org/onap/policy/cds/CdsResponse.java
index fca1aa2e9..499d1a7c9 100644
--- a/models-interactions/model-impl/cds/src/main/java/org/onap/policy/cds/CdsResponse.java
+++ b/models-interactions/model-impl/cds/src/main/java/org/onap/policy/cds/CdsResponse.java
@@ -31,6 +31,7 @@ import lombok.ToString;
@Setter
@ToString
public class CdsResponse implements Serializable {
+ private static final long serialVersionUID = 2590429952699969650L;
private String requestId;
private String status;
diff --git a/models-interactions/model-impl/cds/src/main/java/org/onap/policy/cds/api/CdsProcessorListener.java b/models-interactions/model-impl/cds/src/main/java/org/onap/policy/cds/api/CdsProcessorListener.java
index c07c559c4..fb4c6ed79 100644
--- a/models-interactions/model-impl/cds/src/main/java/org/onap/policy/cds/api/CdsProcessorListener.java
+++ b/models-interactions/model-impl/cds/src/main/java/org/onap/policy/cds/api/CdsProcessorListener.java
@@ -26,7 +26,9 @@ import org.onap.ccsdk.cds.controllerblueprints.processing.api.ExecutionServiceOu
* the received messages appropriately, it needs to implement {@link CdsProcessorListener}.
* </p>
*
- * <p>Here is a sample implementation of a listener:
+ * <p>
+ * Here is a sample implementation of a listener:
+ *
* <pre>
* new CdsProcessorListener {
*
@@ -49,11 +51,10 @@ public interface CdsProcessorListener {
/**
* Implements the workflow upon receiving the message from the server side.
*
- * <p>Note that the CDS client-server communication is configured to use a streaming approach, which means when
- * client
- * sends an event, the server can reply with multiple sub-responses until full completion of the processing. Hence,
- * it is up to the implementation of this method to process the received message using {@link
- * ExecutionServiceOutput#getStatus()#getEventType()}</p>
+ * <p>Note that the CDS client-server communication is configured to use a streaming approach, which means when a
+ * client sends an event, the server can reply with multiple sub-responses until full completion of the processing.
+ * Hence, it is up to the implementation of this method to process the received message using the
+ * getStatus().getEventType() method of {@link ExecutionServiceOutput}
*
* @param message ExecutionServiceOutput received by the CDS grpc server
*/