Re: [Quickfix-developers] Printing Mechanism

[Oren M. <ore...@ya...>]

You should pass a log factory into your initiator or acceptor.  You can choose from either the FileLogFactory (dumps messages to a file), the ScreenLogFactory (dumps them to the screen), or the MySQLLogFactory ( dumps to a... well, you know ).  Or you can create your own.
 
These will show the contents of messages before they pass through validation, allowing you to inspect the actual contents of the message.
 
You can also always print to a stream like so, std::cout << message.toString() << std::endl;

Alok Lal <al...@ra...> wrote:

All,

I'm having a problem validating the expected body length of a
message and the actual body length (ie, what the message says is the body
length and what quickfix calculates to be the body length).

I want to see the guts of the message I've received and I want to
do this particularly in the validate method of Message.h. Does quickfix
have any built in printing mechanism that I can use for debugging to see
the inside of a message header or a field map or trailer? Do I have to
use printf? If so how do I find out the argument types?

Apologies is this is question is a little naive but I really need
to get this workin. Thanks for any help.


Alok




-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
same time. Free trial click here: http://www.vmware.com/wl/offer/345/0
_______________________________________________
Quickfix-developers mailing list
Qui...@li...
https://lists.sourceforge.net/lists/listinfo/quickfix-developers


---------------------------------
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!