xtypes_v2_struct_test_suite_struct_different_ids_ok uses different samples for json and xml

[disganaitis]

dds-xtypes/test_suite.py

Lines 880 to 888 in 2beca33

	'struct_different_ids_ok': {
	'common_args': ['-X xml/types/struct_names.xml'],
	'apps': ['pub-exe -P -t test -y Test::struct_1 -V xml/data/struct_num_x1_x5.xml -J json/data/struct_num_x1_x5.json',
	'sub-exe -S -t test -y Test::struct_2 -V xml/data/struct_num_x1_x5.xml -J json/data/struct_num_x5.json'],
	'expected_codes': [ReturnCode.OK, ReturnCode.OK],
	'check_function': tsf.data_is_correct,
	'title': '',
	'description': ''
	},

The XML data samples assume that members are assigned both based on ID and based on member names which could potentially lead to two publisher members being assigned to one subscriber member, this assumption is not made with the json data

dds-xtypes/xml/types/struct_names.xml

Lines 6 to 14 in 2beca33

	<struct name="struct_1" extensibility="mutable">
	<member name="x1" type="int32" id="1" />
	<member name="x5" type="int32" id="5" /> <!-- so we have a member in common -->
	</struct>
	<struct name="struct_2" extensibility="mutable">
	<member name="x1" type="int32" id="2" />
	<member name="x5" type="int32" id="5" />
	</struct>

dds-xtypes/xml/data/struct_num_x1_x5.xml

Lines 1 to 4 in 2beca33

	<struct>
	<x1>1</x1>
	<x5>5</x5>
	</struct>

dds-xtypes/json/data/struct_num_x1_x5.json

Lines 1 to 4 in 2beca33

	{
	"x1":1,
	"x5":5
	}

dds-xtypes/json/data/struct_num_x5.json

Lines 1 to 3 in 2beca33

	{
	"x5":5
	}