Fix for null dmaap return status 51/89251/1
authorPatrick Brady <patrick.brady@att.com>
Tue, 4 Jun 2019 05:13:50 +0000 (22:13 -0700)
committerTakamune Cho <takamune.cho@att.com>
Tue, 4 Jun 2019 13:48:41 +0000 (13:48 +0000)
commitcc699ebd58f10c947a382ff695a8039f3d0744d8
tree1c01c596f7d178bcdf32698f67315985e622e73e
parent7155b808084ff6e49f6eef01ac7defd9a7754a3a
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
(cherry picked from commit 62433c522bb1feddc2caa22868192edca0b4082f)
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