RTI Router transformation issues

Hi Michael,

Ok let's take a look to the issue. First of all, the error messages do not seem to come from a RS failure but from a dyynamic data failure, so we can discard RS as the error cause. Nevertheless you're on right track pointing that the problem may reside on the bind operation. The probem is that the bound DynamicData object has already a type bound, which is incorrect. If we go to the documentation for the DDS_DynamicData_bind_complex_member operation we see the following:

This operation [DDS_DynamicData_bind_complex_member] is only permitted when the object toBeBound is not currently associated with any type, including already being bound to another member

where in our case, the toBeBound object is the innerEntity, which already has a type bound hence causing the error. In fact I would expect an error after the bind operation (I don't know how the complete stack trace looks like, but it should show that is failing at that point). Otherwise we would need to review code returned by the bind operation).

So what we have to do is to create an untyped DynamicData object as the innerEntity, The way to do this is by passing a NULL type code. Therefore your code should look as folows:

output = DDS_DynamicData_new(self->networkType, &dynamicDataProps);
innerEntity = DDS_DynamicData_new(NULL, &dynamicDataProps); /* type-unbound object */

DDS_DynamicData_bind_complex_member(output,innerEntity,"entity",DDS_DYNAMIC_DATA_MEMBER_ID_UNSPECIFIED);

/* data modifications */

DDS_DynamicData_unbind_complex_member(output, innerEntity)

With these changes the problem should go away :). Let me know what you get.

Antonio

Hi Michael,

Thanks for the files. I've been able to reproduce it. After some research the only I can tell you is that the problem is not due to Routing Service nor Transformation but to DynamicData serialization. You can check that by creating publisher and subscriber in the same domain, and the error keeps showing.

I will keep looking for a workaround but this looks like an internal type serializtion issue.

Antonio

Hello Michael,

I agree with Antonio. The problem seems to be in the DynamicData itself.  

I have tried to reproduce it. However the RAR you attached does not seem to contain all the necessary files to generate all the Java code from the IDL. For example I did not find the IDL file that corresponds to the NetworkTrack type.  I wanted to re-generate the code because I am using a different version of the RTI core libraries and it may affect the generated output...

Short of re-generating from the IDL what I did was create some simple examples of nested types to see if I could reproduce it in a simpler situation. For example I used the type:

module i {
    module o {
        module g {
            module common {
                module iirs {
                    module ddsGen {
                        module infrastructure {
                            struct InnerEntity {
                                long d1;
                                long d2;
                                string<32> d3;
                                long d4;
                            };

                            struct NetworkTrack {
                                InnerEntity entity;
                            };
                        };
                    };
                };
            };
        };
    };		
};

And built a routing service transformation that binds to the inner structure and sets the different "d" attributes. I based the transformation on your code and modified it as Antonio suggested (see attached testtransf.c). This worked without errors. 

I know you are also working with support so perhaps you already have a diagnosis/answer... However, if you are still having trouble and you are able to post here an example with all the IDL files needed to generate the corresponding classes I could take another look... 

Gerardo