|
From: dmd <dm...@co...> - 2008-02-01 02:37:21
|
This solution will work, but it seems rather inefficient, especially for latency sensitive applications, like ours for instance. Will this issue be 'fixed' at some point? Actually, does the FIX spec mandate that tags be in a particular order? Or is it just according to the dictionary's definition? In other words, is the particular aforementioned exchange doing something non-standard? Cheers, Dan toli wrote: > > QuickFIX/J Documentation: http://www.quickfixj.org/documentation/ > QuickFIX/J Support: http://www.quickfixj.org/support/ > David, > >> I was hoping for something that let me do (in effect) >> msg.toString(Dictionary) > > There actually is a quickfix.Message call you can use: > public void fromString(String messageData, DataDictionary dd, > boolean doValidation) > > Will that work of you? you can create one message the "regular way", > then to a toString() on it and use the string-based FIX messgae to > re-create it using a custom dictionary. > > Perhaps that may work for you? > > -- > Toli Kuznets > http://www.marketcetera.com: Open-Source Trading Platform > download.run.trade. > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Quickfixj-users mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfixj-users > > -- View this message in context: http://www.nabble.com/Generate-FIX-string-with-tags-in-a-specific-order--tp12129446p15219578.html Sent from the QuickFIX/J mailing list archive at Nabble.com. |