PFW: No mapping attempt for virtual subsystems

BZ: 15710

Now virtual subsystems overload the mapping process so as to avoid any
object creation attempt.
Object creation only makes sense for concrete subsystems, i.e. those
containing actual physical parameters to be mapped.

Change-Id: Ib7a8d5978ebb79a5d5fecebe3b95cc3bd376cd8e
Signed-off-by: Patrick Benavoli <patrickx.benavoli@intel.com>
Reviewed-on: http://android.intel.com:8080/26099
Reviewed-by: Barthes, FabienX <fabienx.barthes@intel.com>
Tested-by: Barthes, FabienX <fabienx.barthes@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

1 files changed, 19 insertions, 0 deletions

diff --git a/parameter/VirtualSubsystem.cpp b/parameter/VirtualSubsystem.cpp
index ee06fe5..ed708ca 100644
--- a/parameter/VirtualSubsystem.cpp
+++ b/parameter/VirtualSubsystem.cpp
@@ -48,3 +48,22 @@ ISyncer* CVirtualSubsystem::getSyncer() const
 {
     return _pVirtualSyncer;
 }
+
+// From IMapper
+bool CVirtualSubsystem::mapBegin(CInstanceConfigurableElement* pInstanceConfigurableElement, bool& bKeepDiving, string& strError)
+{
+    (void)pInstanceConfigurableElement;
+    (void)strError;
+
+    // Do nothing: prevent any subsystem object from being mapped
+
+    // Stop diving
+    bKeepDiving = false;
+
+    return true;
+}
+
+void CVirtualSubsystem::mapEnd()
+{
+    // Do nothing
+}