resolved jira issue IOT-1014
When scene execute, this issue is caused by not adding scene name
in SceneCollectionResource.
modified parameter in execute API.
Change-Id: I0c78bcd9523f2f425832c0d4934a1b9abd560d81
Signed-off-by: wonny <jw_wonny.cha@samsung.com>
Reviewed-on: https://gerrit.iotivity.org/gerrit/6199
Reviewed-by: JungYong KIM <jyong2.kim@samsung.com>
Reviewed-by: Uze Choi <uzchoi@samsung.com>
Tested-by: Uze Choi <uzchoi@samsung.com>
(cherry picked from commit
53b841669ce6f838d0f964191b42657dbf84b56b)
Reviewed-on: https://gerrit.iotivity.org/gerrit/7697
Tested-by: jenkins-iotivity <jenkins-iotivity@opendaylight.org>
}
m_sceneCollectionResourceObject->setAttribute(
- SCENE_KEY_LAST_SCENE, std::move(sceneName));
+ SCENE_KEY_LAST_SCENE, sceneName);
{
std::lock_guard<std::mutex> memberlock(m_sceneMemberLock);
shared_from_this(), std::move(executeCB));
for (auto & it : m_sceneMembers)
{
- it->execute(sceneName, std::bind(
+ it->execute(std::move(sceneName), std::bind(
&SceneExecuteResponseHandler::onResponse, executeHandler,
std::placeholders::_1, std::placeholders::_2));
}