BidirectionalTopic should use plain TopicSink 07/102807/1
authorJim Hahn <jrh3@att.com>
Tue, 3 Mar 2020 04:43:06 +0000 (23:43 -0500)
committerJim Hahn <jrh3@att.com>
Tue, 3 Mar 2020 04:43:06 +0000 (23:43 -0500)
commita8af78641afbc7af25f78e6c60b1a40475758cec
tree56b104e82850e03f60c3ab44c4f9e3896ffce764
parentd59c619324f5813127e5150e2b3fd5d446cf3a48
BidirectionalTopic should use plain TopicSink

BidirectionalTopicClient use plain TopicSink instead of
TopicSinkClient, because the latter encodes its message, while
BidirectionalTopicClient should not, because encoding should
be left up to the user of the class.

Issue-ID: POLICY-1625
Signed-off-by: Jim Hahn <jrh3@att.com>
Change-Id: I6c67e1ee0c56e96a0efcc90eaf1c0a940902e8b3
policy-endpoints/src/main/java/org/onap/policy/common/endpoints/event/comm/client/BidirectionalTopicClient.java
policy-endpoints/src/test/java/org/onap/policy/common/endpoints/event/comm/client/BidirectionalTopicClientTest.java