[QFJ-478] can not parse cme definition message from cme file Created: 08/Oct/09 Updated: 07/Jul/11 Resolved: 20/Mar/11 |
|
| Status: | Closed |
| Project: | QuickFIX/J |
| Component/s: | Engine |
| Affects Version/s: | 1.4.0 |
| Fix Version/s: | None |
| Type: | Other | Priority: | Default |
| Reporter: | Andrei Pozolotin | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Description |
|
Hello; I can not parse cme definition message from cme file from ftp://ftp.cme.com/secdef.dat.gz code: DataDictionary sessionDictionary, applicationDictionary; sessionDictionary = new DataDictionary("FIXT11.xml"); Message message = new Message(); boolean doValidation = false; message.fromString(messageString, sessionDictionary, sample cme input and quickfixj output: INFO: messageString INFO: message thank you; Andrei |
| Comments |
| Comment by Andrei Pozolotin [ 08/Oct/09 ] |
|
this is due to: |
| Comment by Andrei Pozolotin [ 08/Oct/09 ] |
|
this alleviates the problem: sessionDictionary.setCheckFieldsOutOfOrder(false); but apparently cme needs help; now this: exception=quickfix.FieldException: Tag appears more than once, field=1145 |
| Comment by Andrei Pozolotin [ 08/Oct/09 ] |
|
finally, field=1145 is missing from FIX50.xml need to add: 1) new field definition <field number="1145" name="EventTime" type="UTCTIMEONLY"/> 2) declare this field as member of the group: <component name="EvntGrp"> |
| Comment by Andrei Pozolotin [ 08/Oct/09 ] |
|
quickfix.FieldException: Tag appears more than once, field=1022 |
| Comment by Andrei Pozolotin [ 08/Oct/09 ] |
|
quickfix.FieldException: Tag appears more than once, field=1017 |
| Comment by Andrei Pozolotin [ 08/Oct/09 ] |
|
please let me know how to attach here final FIXCME.xml that works with quickfix 1.4.0? |
| Comment by Jonathan Felch [ 07/Jul/11 ] |
|
The latest build from trunk continues to fail on a large number of records and also continues to be missing field definitions... Technically this file should be depending on FIX 5 SP2, which may be part of the problem... My attempts to generate code for FIX 5 SP 2 were unsuccessful. |