tree 9fa6911affaf1900059f0fde345d74feaef99c22
parent 4d741897f5190720b3cede8da0db9c7f749aa358
author Richard Marian Thomaiyar <richard.marian.thomaiyar@linux.intel.com> 1548688505 +0530
committer Richard Marian Thomaiyar <richard.marian.thomaiyar@linux.intel.com> 1549126527 +0530

Fix: ObjectManager path for asio

For asio based registration, ObjectManager's are created
under "/" folder. This makes dynamic detection difficult based
on the service root object path. Updated library to skip
ObjectManager creation, which can be created separately
by the needed daemon under the root object base path
This is needed, as dynamic detection of service name
can be performed on org.freedeskop.DBus.ObjectManager interface
when the root object doesn't have any interfaces.

Unit-test:
1. Verified it is compiling, and compatibile with existing code
2. Verified that ObjectManager is under the needed base path
when argument passed from service daemon.
3. Able to find service name using GetObject under objectMapper,
when service daemon, doens't have any other interface in root
base path other than org.freedesktop.DBus.Manager

Change-Id: Ie1ddf62df0df3849fc761995813c97872d96eb33
Signed-off-by: Richard Marian Thomaiyar <richard.marian.thomaiyar@linux.intel.com>