Nested Structure - Equivalent IDL

Hi,

I have a nested structure in IDL which I have converted to XML. When I run prototyper with version 5.3.1, then I get the equivalent IDL in Admin console with all the typedefs. However, when I use the same XML file with RTI 6.0.0 then I am not getting the typedefs and the euivalent IDL in admin console shows the typedef values in the structure itself and not the typedefs.

Also, I tried to use the rti dds connector and I am getting the behaviour similar to RTI 6.0.0 as a result I am getting typeconsistency issues with the already built applications using ver 5.3.1.

Could you explain the behaviour and the solution for resolving the compatibility issues between both?

Regards,

Ajay Kumar 

Keywords:

ken

Fri, 07/24/2020 - 08:38

Hi Ajay,

   Would you be able to provide your IDL? That will make it much easier for us to track down the issue. If you have other artifacts, like XML files for QoS/XML Application Creation/Prototyper configuration/Connector code, those would also be a big help in determining what's going on here. Also, just to be clear, you're using the same files between 5.3.1 and 6.0.0 and the resulting IDL from Admin Console is quite different and you're having type compatibility fail with 6.0.0 whereas it works with 5.3.1. Is that right? Between which two applications (and version) is the type compatibility failing?

Thanks,
Ken

kumar.ajay11

Wed, 07/29/2020 - 04:07

Hi Ken,

I have attached IDL, XML to track down the issue alongwith the document with snapshots showing mismatch for reference.

I had used the IDL to generate the Example Code with RTI 5.3.1 and ran the Subscriber. Then I ran the prototyper of RTI 6.0.0with the ShapeExample.xml attached for publishing the topics. After this not matched was observed in RTI Admin 5.3.1

Regards,

Ajay

File Attachments: 
File shapeexample.xml
Binary Data shape.idl
PDF icon type_mismatch_issue.pdf

ken

Fri, 08/07/2020 - 12:21

Hi Ajay,

   Sorry for the delays...I was able to reproduce the issue and am in the process of investigating it but I'm about to go on vacation for 2 weeks. I'll be playing catch up for the week I come back and will try to continue the investigation after that.

   By the way, below is a screenshot comparing the types in different configurations. While 6.0.0 has a bit more data, nothing obvious stands out to me (except it appears that @min & @max has a bug...will investigate that too).

Thanks,
Ken

 

kumar.ajay11

Fri, 08/07/2020 - 21:39

Hi Ken,

Thanks for the update.

Is it possible for you to share the link to download rti dds connector compatible for 5.3.1 in the meantime for node.js, so that I can check with that version?

Regards,

Ajay

alexc

Mon, 08/24/2020 - 13:19

Hi Ajay,

Connector is only supported on 6.0.1 (Connector v1.0.0). Previous version were experimental and are no longer supported.

ALex

kumar.ajay11

Fri, 09/04/2020 - 03:41

Hi Alex,

I understand that Connector is only supported on 6.0.1. But does that mean if I have a subscriber on 5.3.1 and use this connector (i.e. V 1.0.0) for publishing, then they will be incompatible specially if idl contains sequences.

Ajay

alexc

Fri, 09/04/2020 - 08:51

They should be compatible, I'll take a look at your files to see what's going on.

alexc

Fri, 09/04/2020 - 09:13

Can you also provide information about the type incompatibility? You can see that in the Admin console matching analysis or by enabling warning verbosity in the DDS application.