Beacon-based Tango database server gives duplicated device classes
Hi,
When creating a device server with more than one class on a system with a beacon-based Tango database server, Jive shows the same device under two different classes.
The following tango/Toto_a1.yml
YAML file:
server: Toto
personal_name: a1
device:
- tango_name: id99/toto/1
class: Toto
- tango_name: id99/tata/1
class: Tata
- tango_name: id99/toto_bla/1
class: Toto_bla
- tango_name: id99/tata_bla/1
class: Tata_bla
- tango_name: id99/toto_bla_2/1
class: Toto_bla_2
- tango_name: id99/tata_bla_2/1
class: Tata_bla_2
produces a wrong Jive device structure:
It looks like if a device is reported to belong to all the classes whose names match the device class.
Can you please tell what is wrong?
Cheers