Bug fix in DMAAP message parsing for CMNotify

Minor bug fix in the DMAAP message for CMNotify

Issue-ID: CCSDK-2383
Signed-off-by: SandeepLinux <Sandeep.Shah@ibm.com>
Change-Id: Ia080adafecf6d6b3a12682aaab3f244a33a16de5

diff --git a/dmaap-listener/src/main/java/org/onap/ccsdk/sli/northbound/dmaapclient/CMNotifyDmaapConsumer.java b/dmaap-listener/src/main/java/org/onap/ccsdk/sli/northbound/dmaapclient/CMNotifyDmaapConsumer.java
index e49e77e..fa14fbb 100644 (file)
--- a/dmaap-listener/src/main/java/org/onap/ccsdk/sli/northbound/dmaapclient/CMNotifyDmaapConsumer.java
+++ b/dmaap-listener/src/main/java/org/onap/ccsdk/sli/northbound/dmaapclient/CMNotifyDmaapConsumer.java
@@ -71,14 +71,10 @@ public class CMNotifyDmaapConsumer extends SdncDmaapConsumerImpl {
             return;
         }
 
-        JSONObject rpcMsgBodyNode = new JSONObject();
-
-        rpcMsgBodyNode.put(INPUT,payloadNode);
-
         String rpcMsgbody;
         try {
                ObjectMapper mapper = new ObjectMapper();
-                rpcMsgbody = mapper.writeValueAsString(rpcMsgBodyNode);
+                rpcMsgbody = "{\"input\":" + mapper.writeValueAsString(payloadNode) + "}";
 
         } catch (Exception e) {
             LOG.error("Unable to parse payload in CMNotify-DMAAP message", e);