Fix for null dmaap return status 08/89208/2
authorPatrick Brady <patrick.brady@att.com>
Tue, 4 Jun 2019 05:13:50 +0000 (22:13 -0700)
committerPatrick Brady <patrick.brady@att.com>
Tue, 4 Jun 2019 05:56:49 +0000 (22:56 -0700)
commit62433c522bb1feddc2caa22868192edca0b4082f
treed4d0d516303c29ca0d39f42bc9f568f506da004f
parentbd1da0d90b12f36f2931e8b3dba4cfb63ef3442b
Fix for null dmaap return status

The setResponse method was returning before actually
setting the status values in cases where the status
field was not first initialized. This behavior did
not make sense since the status field would never be
initialized in cases where the OutgoingMessage was
generated using the IncomingMessage.toOutgoing().

Change-Id: Ib399daf3644095a2eeffe718d0f6a27473b01ee9
Signed-off-by: Patrick Brady <patrick.brady@att.com>
Issue-ID: APPC-1619
appc-event-listener/appc-event-listener-bundle/src/main/java/org/onap/appc/listener/demo/model/OutgoingMessage.java
appc-event-listener/appc-event-listener-bundle/src/test/java/org/onap/appc/listener/demo/model/TestIncomingMessage.java