{{Quickfixn}} FpML file

[Ashutosh Mishra]

I am able to retrieve firleds form the execution report and I am not using any message queue -- The Execution Report that comes in from the other part I am directly taking it and using the FIX engine to retrieve the fields.
Is there a better way to do the same? Further how can I figure out, programatically, which fields are in the header abd which in the body?

Thanks & Regards,
Ashutosh Mishra

*********************************************************************************
This communication (including any attachments) is intended only or the use of the individual whom it is addressed and may contain information that is privileged, confidential or legally protected.  If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message.  Please also delete the message and its attachments, if any, from your computer and destroy any hard copies you may have created.  Thank you for your cooperation.
*********************************************************************************

From: quickfixn-bounces at lists.quickfixn.com [mailto:quickfixn-bounces at lists.quickfixn.com] On Behalf Of Grant Birchmeier
Sent: Thursday, October 31, 2013 2:45 PM
To: Mailing list for QuickFIX/n
Subject: Re: {{Quickfixn}} FpML file

You don't invoke them, you only implement them.  When the engine receives a message, it will invoke the appropriate OnMessage(type) function that you defined.

Please read through the tutorial pages:
http://quickfixn.org/tutorial/creating-an-application

See the "Receiving Messages" page (link on sidebar).

(If you receive a message type for which you have not defined an OnMessage(), then the engine will assume you don't want to support that message and will send a reject.)


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.quickfixn.com/pipermail/quickfixn-quickfixn.com/attachments/20131104/aa2b9da2/attachment-0002.htm>