Originally Opened: @Alfiva (2015-06-30 11:07:03)
Originally Closed: 2015-06-30 11:12:49
The activator, factory and ontology classes of ont.device.extra have the same name as in ont.device, i.e: DeviceActivator, etc...
That is not a problem per se, but it leads to some issues in Android (that's a problem of its own), and more importantly, it leads to errors in serialization (critical when there are 2 instances or more).
During serialization it is used the factory class of each ontology. Because the name DeviceFactory is the same in ont.device.extra and ont.device, and ont.device is registered first, serialization uses the DeviceFactory of ont.device in both cases, thus serializing e.g. a SirenActuator from ont.device.extra as a WindowActuator, because they are ID Nr. 2 in the factories.
The names of the common classes in ont.device.extra have to be changed.
--
From: this issue has been automatically imported from our old issue tracker
Originally Opened: @Alfiva (2015-06-30 11:07:03) Originally Closed: 2015-06-30 11:12:49
The activator, factory and ontology classes of ont.device.extra have the same name as in ont.device, i.e: DeviceActivator, etc...
That is not a problem per se, but it leads to some issues in Android (that's a problem of its own), and more importantly, it leads to errors in serialization (critical when there are 2 instances or more).
During serialization it is used the factory class of each ontology. Because the name DeviceFactory is the same in ont.device.extra and ont.device, and ont.device is registered first, serialization uses the DeviceFactory of ont.device in both cases, thus serializing e.g. a SirenActuator from ont.device.extra as a WindowActuator, because they are ID Nr. 2 in the factories.
The names of the common classes in ont.device.extra have to be changed.
--
From: this issue has been automatically imported from our old issue tracker