Imported from previous forum
Hi FIX Spec WG,
In General Q/A forum, I had mentioned a problem loading FIXT.1.1 + FIX.5.0 repositories together which I am posting here for further discussion.
[Start Quote from http://www.fixprotocol.org/discuss/read/6716e28d ]
The problem I found with loading the FIXT.1.1 + FIX.5.0 repositories together was that when loading MsgType.xml my engine was expecting MsgType to be unique, so after loading FIXT.1.1 repository, when it starts loading the FIX.5.0 repository, it complains about duplicate MsgType, throws an exception and exits. I handled it by manually editing the FIX.5.0 repository and removing all the Session level MsgTypes which were already present in FIXT.1.1 repository. This worked, but I found it a dirty solution and didn’t like it. I want to be able to deploy the FIX repository for a new version without any manual edits.
[End quote]
[Start Jim Northey’s reply]
The approach we have come up with is to create configuration rules that define how to handle fields that overlap. For instance MsgType=D should be unknown to FIXT.1.1 But MsgType=D is known for FIXT.1.1+FIX.[45]*
There are other fields. Phil and Ryan did separate analyses on this. We are close to having both: 1) Configuration rules for dynamically binding and 2) producing static, pre-configured repositories for use by member firms.
[End reply]
Regards,
K. Mahesh