QuickFIX/JIcon indicating the project type

QuickFIX/J

Uploaded image for project: 'QuickFIX/J'
  1. QuickFIX/J
  2. QFJ-170

Repeating group not parsed correctly

          Details

          • Type: Bug
          • Status: Closed
          • Priority: Default
          • Resolution: Not a bug
          • Affects Version/s: 1.1.0
          • Fix Version/s: None
          • Component/s: Message Generation
          • Labels:
            None
          • Environment:
            Windows

            Description

            The attached program creates a NewOrderSingle message with a NoAllocs group repeating twice. It converts the message to a string and then parses the string back to a message. Unfortunately one instance of the repeating group is lost, only one instance shows up when the parsed message is converted back to a string. I really hope that I am overlooking something!

              Attachments

                Activity

                Ascending order - Click to sort in descending order
                Hide
                Permalink
                nbhatia Naresh Bhatia added a comment -

                BTW, here's the output from the sample program. The two message strings should be equal, but they are not:

                Message1: 8=FIX.4.49=14135=D34=10049=COOLTRD52=20070501-00:17:2556=MA11=ORDER_3091738=100.540=154=155=IBM60=20070501-00:17:2578=279=Account179=Account210=205

                Message2: 8=FIX.4.49=12935=D34=10049=COOLTRD52=20070501-00:17:2556=MA11=ORDER_3091738=100.540=154=155=IBM60=20070501-00:17:2578=279=Account210=039

                Note that Account1 is missing from Message2.

                Show
                nbhatia Naresh Bhatia added a comment - BTW, here's the output from the sample program. The two message strings should be equal, but they are not: Message1: 8=FIX.4.49=14135=D34=10049=COOLTRD52=20070501-00:17:2556=MA11=ORDER_3091738=100.540=154=155=IBM60=20070501-00:17:2578=279=Account179=Account210=205 Message2: 8=FIX.4.49=12935=D34=10049=COOLTRD52=20070501-00:17:2556=MA11=ORDER_3091738=100.540=154=155=IBM60=20070501-00:17:2578=279=Account210=039 Note that Account1 is missing from Message2.
                Hide
                Permalink
                admin Steve Bate added a comment -

                To parse a message with a repeating group, you must include a data dictionary. The data dictionary provides metadata to know which fields are part of repeating groups. Your test program did not use a DD when parsing the message. After adding the DD argument to the message constructor, the test worked correctly.

                Show
                admin Steve Bate added a comment - To parse a message with a repeating group, you must include a data dictionary. The data dictionary provides metadata to know which fields are part of repeating groups. Your test program did not use a DD when parsing the message. After adding the DD argument to the message constructor, the test worked correctly.
                Hide
                Permalink
                admin Steve Bate added a comment -

                By the way, thanks for the test case.

                Show
                admin Steve Bate added a comment - By the way, thanks for the test case.
                Hide
                Permalink
                nbhatia Naresh Bhatia added a comment -

                Thanks Steve. It works beautifully after adding the data dictionary. Perhaps this would be a useful tip to add to the docs.

                Show
                nbhatia Naresh Bhatia added a comment - Thanks Steve. It works beautifully after adding the data dictionary. Perhaps this would be a useful tip to add to the docs.

                  People

                  • Assignee:
                    admin Steve Bate
                    Reporter:
                    nbhatia Naresh Bhatia
                  • Votes:
                    0 Vote for this issue
                    Watchers:
                    0 Start watching this issue

                    Dates

                    • Created:
                      Updated:
                      Resolved: