Menu
▾
▴
Re: [Quickfixj-users] Ordering message tags
|
From: Christoph J. <chr...@ma...> - 2020-06-08 13:39:42
|
Do you also have a custom message factory? Otherwise I think that the tags get reordered again on processing of a ResendRequest because the Message is parsed from a String in the message store. Cheers, Chris. On 08.06.20 13:06, Philip Whitehouse wrote: > We have an internal build that provides a FieldMap constructor with a field order and then uses > that to assign a TreeMap instead of a LinkedHashMap. > > This seems to work. > > Best, > Philip Whitehouse > >> On 8 Jun 2020, at 11:06, Christoph John via Quickfixj-users >> <qui...@li...> wrote: >> >> QuickFIX/J Documentation: http://www.quickfixj.org/documentation/ >> QuickFIX/J Support: http://www.quickfixj.org/support/ >> >> >> Hi, >> >> if you want to enforce a specific tag ordering in outgoing messages then you have two options: >> 1. Recompile QuickFIX/J with a data dictionary with your desired order of tags. This is the clean >> approach. >> 2. Extend quickfix.Message and specify the tag ordering. This programmatic approach has some >> drawbacks. See this for instructions: https://stackoverflow.com/a/60048848/4962355 >> >> Cheers, >> Chris. >> >> >> >> On 08.06.20 11:16, Taysay Shaguy wrote: >>> QuickFIX/J Documentation:http://www.quickfixj.org/documentation/ >>> QuickFIX/J Support:http://www.quickfixj.org/support/ >>> >>> >>> >>> Thank you Grant most especially for helping drive this community. I see your helping hand all >>> over, stackoverflow and all. >>> >>> Yes I have that in place, however for some reason the exchange I am connecting too wants some >>> tags in a specific order particularly for >>> >>> " TradeCaptureReportRequest" with the tags 568, 569, 580, 75. I noticed that the message is >>> sent it reorders to 75, 568, 569, 580, then the exchange complains of tag 75, however, using >>> miniFix it works. That's the reason I want to manually reorder my code. >>> >>> >>> >>> >>> >>> On Sun, Jun 7, 2020 at 10:31 PM Grant Birchmeier <gbi...@co... >>> <mailto:gbi...@co...>> wrote: >>> >>> QuickFIX/J Documentation: http://www.quickfixj.org/documentation/ >>> QuickFIX/J <http://www.quickfixj.org/documentation/QuickFIX/J> Support: >>> http://www.quickfixj.org/support/ >>> >>> >>> Field order is only relevant within repeating groups. >>> >>> In the top-level body, outside of groups (and outside of header and trailer), the order is >>> irrelevant. >>> >>> For repeating groups to work right, you need DataDictionary=path/to/your/FIXnn.xml, and >>> UseDataDictionary=Y. >>> >>> On Sun, Jun 7, 2020 at 2:44 AM Taysay Shaguy <tay...@gm... >>> <mailto:tay...@gm...>> wrote: >>> >>> QuickFIX/J Documentation: http://www.quickfixj.org/documentation/ >>> QuickFIX/J <http://www.quickfixj.org/documentation/QuickFIX/J> Support: >>> http://www.quickfixj.org/support/ >>> >>> >>> Dear All, >>> >>> Please is there a way to order my request tags either by configuration or >>> programmatically the exchange I am pointing to requires certain messages to have tags in >>> a defined order. >>> >>> I am using QuickFixJ 2 11. So while my reques works on MiniFix it complains about "tag >>> not being defined for message type" for the same message tag just ordered differently. >>> >> >> -- >> Christoph John >> Software Engineering >> T +49 241 557080-28 >> chr...@ma... >> >> MACD GmbH >> Oppenhoffallee 103 >> 52066 Aachen, Germany >> www.macd.com >> >> Amtsgericht Aachen: HRB 8151 >> Ust.-Id: DE 813021663 >> Geschäftsführer: George Macdonald >> _______________________________________________ >> Quickfixj-users mailing list >> Qui...@li... >> https://lists.sourceforge.net/lists/listinfo/quickfixj-users -- Christoph John Software Engineering T +49 241 557080-28 chr...@ma... MACD GmbH Oppenhoffallee 103 52066 Aachen, Germany www.macd.com Amtsgericht Aachen: HRB 8151 Ust.-Id: DE 813021663 Geschäftsführer: George Macdonald |
