[Quickfix-developers] Problems migrating from 1.0.4 to 1.3.2
Brought to you by:
orenmnero
From: Bernard S. <bsp...@gx...> - 2003-02-27 23:16:10
|
This week, I finally decided to upgrade from 1.0.4 to 1.3.2 to see how it= went. I have a server application and a client application. The server= application needed only 1 small change to make it compile. The first ar= guments to the following 2 functions appear to no longer be const: =20 void toAdmin( FIX::Message&, const FIX::SessionID& ) {} void toApp( FIX::Message&, const FIX::SessionID& ) =20 I'm pleased to say that once I made the change, my server application com= piled and ran through all the scenarios I tested without problems. =20 My client app has another problem. It required the same changes, but onc= e made, it started blowing up right at the line shown below. For some re= ason, it is unable to find the session in the collection. I'll trace thr= ough tomorrow to see what's going on, but if anyone is aware of a change = between these releases that would save me the time, I'd be very grateful! =20 =20 bool Session::sendToTarget( Message& message ) throw( SessionNotFound& ) { try { SessionID sessionID =3D message.getSessionID(); Session* pSession =3D lookupSession( sessionID ); if ( !pSession ) throw SessionNotFound(); ------------------------= ----------------------------------> Right here! bool result =3D pSession->send( message ); return result; } catch ( FieldNotFound& ) { throw SessionNotFound(); } } =20 =20 ------------------------------------------ Bernard Spanger bsp...@gx... G. X. Clarke & Co. 10 Exchange Place Jersey City, NJ 07302 201-200-3607 =20 =0D =0D Confidentiality. This message (including any attachments) (collectively= , the "Material") may contain confidential information and is intended on= ly for a specific individual and purpose. If you are not the intended re= cipient, any copying, disclosure, distribution or other use of the Materi= al, or the taking of any action in reliance on the information contained = therein, is strictly prohibited. If you have received the Material in er= ror, please immediately notify us by telephone and delete the Material an= d all copies thereof from your computer and network. No Investment Advice, Offer or Solicitation; Suitability. The Material h= as been prepared for informational purposes only without regard to any pa= rticular user's investment objectives, financial situation or means and d= oes not constitute an offer, solicitation or recommendation to take any a= ction. We are not providing investment advice, nor do we represent that = any securities or services described in the Material are suitable for a p= articular client. Before acting on the Material, each client should make= its own determination whether information contained therein is suitable = for its particular circumstances, and if necessary consult with a senior = officer. Conflicts. We, or persons involved in the preparation of issuance of the= Material, may from time to time effect transactions, or have positions i= n the securities mentioned in the Material (or options or futures contrac= ts with respect thereto). Disclaimer. Although the Material is based upon information that we cons= ider reliable, we do not warrant that the Material is reliable, accurate = or complete and it should not be relied upon as such. Neither we, nor any= of our affiliates or agents shall have any responsibility whatsoever for= any direct, indirect, consequential, special or other damages or lost pr= ofits or savings or other economic harm your may suffer as a result of yo= ur reliance on the Material or the reliability, accuracy, or completeness= thereof. We expressly disclaim all express and implied warranties, incl= uding, without limitation, warranties of merchantability and fitness for = a particular purpose. --------------------------------------------- -Checked for viruses by McAfee.- o1 ---------------------------------------------=0D |