Eliminate result code from RCSGetResponse and RCSSetResponse.
authorcoderhyme <jhyo.kim@samsung.com>
Fri, 18 Sep 2015 11:02:46 +0000 (04:02 -0700)
committerMadan Lanka <lanka.madan@samsung.com>
Sat, 19 Sep 2015 06:56:52 +0000 (06:56 +0000)
commit624d4e25650d82ec593fabb3f83f4a430fa3387b
treecece2b9173561d2ee90e09df17bf0253fb24df2c
parent817f404d2b6143fabae858fd378882c7b8fa6eb0
Eliminate result code from RCSGetResponse and RCSSetResponse.

It turned out there is no reason for users to set the result code.
The only scenario that RCSResponses have not OK for the result is that there is an error occurred
and in that case it should be an exception on resource-encapsulation layer.

Change-Id: Icef409ea5e224f9f02e12e174231baa4e11c5a33
Signed-off-by: coderhyme <jhyo.kim@samsung.com>
Reviewed-on: https://gerrit.iotivity.org/gerrit/2705
Tested-by: jenkins-iotivity <jenkins-iotivity@opendaylight.org>
Reviewed-by: Madan Lanka <lanka.madan@samsung.com>
service/resource-encapsulation/android/service/src/main/jni/JniRcsResourceObject.cpp
service/resource-encapsulation/include/RCSResponse.h
service/resource-encapsulation/src/resourceContainer/src/ResourceContainerImpl.cpp
service/resource-encapsulation/src/serverBuilder/include/RequestHandler.h
service/resource-encapsulation/src/serverBuilder/src/RCSResponse.cpp
service/resource-encapsulation/src/serverBuilder/src/RequestHandler.cpp
service/resource-encapsulation/src/serverBuilder/unittests/RCSResourceObjectTest.cpp
service/resource-encapsulation/src/serverBuilder/unittests/RCSResponseTest.cpp
service/resource-encapsulation/src/serverBuilder/unittests/RequestHandlerTest.cpp
service/resource-encapsulation/unittests/ResourceClientTest.cpp