[xsd-users] XSD Generate Extraction and Ordered Type

[Southworth Damon (AA-AS/EOS32)]

Hi Boris,

Thanks for the extra information, I think the example "ordered type" that I serialised was just too simple so I just got away with it. I admit that I have not run all our unit tests on the code using the binary serialisation yet as the build pipe line fails due to NO ordering information being generated so the list appears empty at the moment.

> or save the ordering information in some other way

I did wonder when looking at the generated code, why the content_order_ vector was not serialised along with the data items so it could be extracted on de-serialisation and the information preserved?

Thanks,

Damon.


-----Original Message-----
From: Boris Kolpackov [mailto:boris at codesynthesis.com] 
Sent: 08 September 2016 17:19
To: Southworth Damon (AA-AS/EOS32) <damon.southworth at uk.bosch.com>
Cc: xsd-users at codesynthesis.com
Subject: Re: [xsd-users] XSD Generate Extraction and Ordered Type

Hi Damon,

Southworth Damon (AA-AS/EOS32) <damon.southworth at uk.bosch.com> writes:

> Manually editing the generated code allowed the binary serialisation 
> to work correctly.

This is actually a lot trickier than that. To preserve element order in binary extraction you first need to insert them in the correct order (or save the ordering information in some other way). I've started working on this and it got pretty hairy very quickly. I will need to think some more on it in the next couple of days.

Boris