Re: [Quickfix-developers] catch getField business rejects

[Oren M. <or...@qu...>]

Yeah.  The fromApp method normally propogates the FieldNotFound error, 
which the session catches and send a reject indicating the conditionally 
required field is missing.  If you want to handle this yourself, you 
would wrap the implementation of your method in a try/catch block and 
trap the exception.  You can then handle it yourself, and rethrow if you 
would like the session to also send its normal reject.

--oren

John GALLET wrote:

>QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html
>QuickFIX Support: http://www.quickfixengine.org/services.html
>
>Hi there,
>
>The more different Fix engines I connect to, the more I see that no one 
>cares about conditionnaly required fields. So very often, I use a 
>getField() method that fails and sends a Business Reject. The counterparty 
>then complains about this (well of course, they don't send the correct 
>data so it's only logical they should complain when they are told they 
>don't). Anyway, I'd rather not have to always use the 
>if(isSetField(...)){getField()...} construct when I *know* the message is 
>supposed to have the tag, but at the same time, manage the error myself. 
>
>What would be the central point for catching which exception to do that ? 
>The fromApp() method catching FIX::FieldNotFound ?
>
>TIA
>JG
>
>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
>Register for a JBoss Training Course.  Free Certification Exam
>for All Training Attendees Through End of 2005. For more info visit:
>http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
>_______________________________________________
>Quickfix-developers mailing list
>Qui...@li...
>https://lists.sourceforge.net/lists/listinfo/quickfix-developers
>
>
>  
>