This is related to QFJ-472

I noted another approach as in QFJ-483

Hi please find attached a patch which addresses FIX 5.0 SP2 in FIXVersions.java, MessageCracker.java, MessageUtils.java and FIX50.xml, FIXT11.xml.

I tried to follow the existing idiom in QuickFIXJ for FIX 5, but took the approach of treating SP1, SP2 as specialisations of FIX50.xml. In this approach one configured instance of the FIX gateway would not support FIX50 and FIX50SP2 as distinct versions. I only added the ApplVerId to the FIX50.xml leaving it as an exercise for the user to add support for the messages and fields which they will implement.

Please note the more complete approach to the dictionary in QFJ-483.

I hope this will help, if there is any feedback to make this fit in better with plans for QuickFixJ please let me know. I can try to assist if it will help.

Hi,

We're trying to use "Trade Capture Report message (AE)" message from LSE "Own Trade Book Download" service.

LSE use AppVerId=9 (FIX5.0SP2)

• MessageUtils.toBeginString(ApplVerID applVerID) return null
• DataDictionary getApplicationDataDictionary(ApplVerID applVerID) return a null dictionnary
• in Message.parseBody(DataDictionary dd, boolean doValidation), repeating groups are discarded

Is there a workaround for this problem other than patching quickfix/j ?

Christophe, I'm afraid there is no workaround.

Committed as rev #1079.

Added application data dictionaries for SP1 and SP2. They were generated with the generator from QFJ-483.
Please note that code generation based on this dictionaries does not work correctly due to the following issues:

• FIX5.0: fields LegPrice and LegOptionRatio are duplicated in some components. This is a specification problem which was rectified in SP1.
• FIX5.0 SP1/2: component (Derivative)SecurityXML has a field of the same name which causes duplicate identifiers in the generated code
• FIX5.0 SP2: components StrmAsgnReqGrp and StrmAsgnRptGrp are repeating groups but have no delimiter field.
  These issues can be avoided by manually tweaking the data dictionary prior to code generation.