Fix to use OC_IPV4 instead of OC_ALL in Things Manager

When constructResourceObject function is used, OC_ALL parameter is not
working well. Instead of this, OC_IPv4 parameter can be used.

Change-Id: I5652551b844dd3d4a15af0392c170535db68dd8b
Signed-off-by: Jihun Ha <jihun.ha@samsung.com>
Reviewed-on: https://gerrit.iotivity.org/gerrit/1059
Tested-by: jenkins-iotivity <jenkins-iotivity@opendaylight.org>
Reviewed-by: Uze Choi <uzchoi@samsung.com>

diff --git a/service/things-manager/sdk/src/ThingsConfiguration.cpp b/service/things-manager/sdk/src/ThingsConfiguration.cpp
old mode 100644 (file)
new mode 100755 (executable)
index 43c6895..4ea8804
--- a/service/things-manager/sdk/src/ThingsConfiguration.cpp
+++ b/service/things-manager/sdk/src/ThingsConfiguration.cpp
@@ -326,7 +326,7 @@ namespace OIC
 
             std::string host = getHostFromURI(oit->getUri());
 
-            tempResource = OCPlatform::constructResourceObject(host, uri, OC_ALL, true,
+            tempResource = OCPlatform::constructResourceObject(host, uri, OC_IPV4, true,
                     oit->getResourceTypes(), m_if);
 
             p_resources.push_back(tempResource);