FIXML message version

, ,
1

Imported from previous forum

2

Hi all,

When a new protocol version is introduced there needs to be a migration process to move the services forward onto the new version. It is relatively straightforward for the code generator to warn that a service is using an old version.

In that case same message receiver is not able to distinguish which version of this message is expecting so are there any ways to resolve this question?

Thanks in advance

3

FIXML does not have a separate versioning, it is identical to FIX versions. These can be expressed in the following FIX fields:
1128 ApplVerID
1156 ApplExtID
1129 CstmApplVerID
Please see the FIX 5.0 SP2 Errata Specification Volume 1, page 32 to find the equivalent FIXML attributes (v,xv,xc whereas r and xr have been deprecated).
Regards,
Hanno.

Hi all,

When a new protocol version is introduced there needs to be a migration process to move the services forward onto the new version. It is relatively straightforward for the code generator to warn that a service is using an old version.

In that case same message receiver is not able to distinguish which version of this message is expecting so are there any ways to resolve this question?

Thanks in advance