Re: [Quickfix-developers] ValidateFieldsHaveValues=N

[Scott K. <sc...@la...>]

Found the bug id...
http://sourceforge.net/tracker/?func=detail&aid=3024822&group_id=37535&atid=1126912

seems to be fixed now... perhaps I should upgrade...

On Tue, Jan 18, 2011 at 5:20 PM, Scott Kathrein
<sc...@la...>wrote:

> I find that this setting doesn't work when UseDataDictionary=N
>
> Tracing through the code, I see that the three Validate settings (*
> ValidateFieldsOutOfOrder, **ValidateFieldsHaveValues, **
> ValidateUserDefinedFields)* are not even checked at all when
> UseDataDictionary is false.  In the code, I see that a default constructed
> "DataDictionary emptyDataDictionary;" is used from DataDictionaryProvider,
> which has
>
> bool m_checkFieldsOutOfOrder;
> bool m_checkFieldsHaveValues;
> bool m_checkUserDefinedFields;
>
> all set to true, and this empty data dictionary is used to do validation on
> the message. Of course, I do not want any validation to be done on the
> message(!), beyond the basics. Is this a known bug?
>
> I love quickfix and I think it's beautifully constructed. I've already
> commandeered its HTTP server for my own front end to my application, and I
> plan to do other things with the logging as well! Be nice if some of these
> things were better tested.. maybe I can do my part here..
>
> Scott
>