[This message was posted by Franz Kettwig of Concord Energy, LLC <[EMAIL PROTECTED]> to the "FAST Protocol" discussion forum at http://fixprotocol.org/discuss/46. You can reply to it on-line at http://fixprotocol.org/discuss/read/fe32479c - PLEASE DO NOT REPLY BY MAIL.]
I noticed the same thing. The latest java sample code on the site works correctly. However, if you would like to update your current code: com.cme.fest.protocol.fast.FastTemplateIdDecoderStrategy.java: line 63 - change to decode a UInt32 and the templateID variable needs to be extracted using getUnsignedInteger() I have not used the CME sample encoder, but I assume that there is a symmetric bug there also. Franz > We just started running the CME's java sample code - it worked correctly > on all our test data, but when we hooked it up to the feed we found that > the decoder occasionally throws. Evidently, the decoder is treating > template ID's as signed ints rather than unsigned ints. Has anyone else > had this problem? If the fix is simple, a code snippet would be greatly > appreciated. [You can unsubscribe from this discussion group by sending a message to mailto:[EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Financial Information eXchange" group. To post to this group, send email to FIX-Protocol@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/FIX-Protocol?hl=en -~----------~----~----~----~------~----~------~--~---
