Removed clientCB delete logic when we received error from CA
authorhyuna0213.jo <hyuna0213.jo@samsung.com>
Thu, 11 Aug 2016 08:08:20 +0000 (17:08 +0900)
committerAshok Babu Channa <ashok.channa@samsung.com>
Fri, 26 Aug 2016 05:31:00 +0000 (05:31 +0000)
commit09b286b7ed683bcfd4b24d2f6025898b0ac410a4
tree1a394ed29fc2a34441b1f2c888bcdef6c1d537b7
parent081e13cd10c7b30780d82f331ceb4544d02459d7
Removed clientCB delete logic when we received error from CA

If we remove clientCB when we received error message from CA,
we cann't receive the other response message in case request message
is sent over multi transport. so clientCB shouldn't be removed.

Change-Id: I5289fe4892a32f7da1d84cf3f50493e260e4eada
Signed-off-by: hyuna0213.jo <hyuna0213.jo@samsung.com>
Reviewed-on: https://gerrit.iotivity.org/gerrit/10257
Tested-by: jenkins-iotivity <jenkins-iotivity@opendaylight.org>
Reviewed-by: Jaehong Jo <jaehong.jo@samsung.com>
Reviewed-by: Ashok Babu Channa <ashok.channa@samsung.com>
android/android_api/base/jni/JniOnResourceFoundListener.cpp
resource/csdk/stack/src/ocstack.c