Re: [Quickfix-users] ValidateUserDefinedFields=N doesn't work in the [DEFAULT] Section Of a settings file in Quickfix 1.13.2

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

Hmmm.  Doesn't look like the implementation has changed.  And the  
document does say ValidateUserDefinedFields defaults to true.  Are you  
sure that you did not replace the data dictionary file with one not  
containing those fields?

On Mar 26, 2010, at 11:19, sevzas <se...@gm...> wrote:

> QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html
> QuickFIX Support: http://www.quickfixengine.org/services.html
>
>
> I'm upgrading Quickfix from 1.12.4 to 1.13.2.  I use QuickFix with  
> a .NET 3.5
> app.
>
> I took existing code that works and simply changed the references  
> point to
> the new QuickFix 1.13.2.
>
> What I'm seeing is that messages with custom tags are now being  
> rejected by
> my app.
>
> I get messages like (tags 49 and 56 are changed)
> 8=FIX. 
> 4.2 
> 
9= 
> 119
 
> 35= 
> 3
3 
> 4=2 
> 39
 
> 49= 
> XXXX
 
> 50=0001
52=20100326-13:56:00.406
56=XXXX
57=TEST
45=240
58=Invalid
> tag number
371=9621
372=8
373=0
10=144

>
> This message is a rejection of tag 9621 which is a custom tag sent  
> by an
> ECN.  I would like custom fields to be accepted by my app like they  
> were
> with the old version of QuickFix.
>
> My config file is built from pieces by my code, but looks like this  
> before
> creating a session (some parms are changed):
>
> [DEFAULT]
> ConnectionType=initiator
> BeginString=FIX.4.2
> CheckCompID=N
> CheckLatency=N
> StartTime=00:00:00
> EndTime=00:00:00
> HeartBtInt=5
> MaxLatency=120
> ReconnectInterval=1
> UseDataDictionary=Y
> ValidateFieldsHaveValues=N
> ValidateFieldsOutOfOrder=N
> ValidateUserDefinedFields=N
> SocketNoDelay=Y
> PersistMessages=Y
> [SESSION]
> DataDictionary=FIX42.xml
> SenderCompID=BD
> SenderSubID=0001
> SocketConnectHost=111.22.33.44
> SocketConnectPort=12345
> TargetCompID=ECN
> TargetSubID=TEST
>
> When I move the "ValidateUserDefinedFields=N" to the [SESSION]  
> section, it
> seems to work fine.  So there is a work-around but it requires a  
> change.  I
> also fear that some of the other ValidateXXXXX settings do not work  
> properly
> in the [SESSION] section.
>
> Can anyone out there confirm the problem and does anyone know an ETA  
> for a
> fix?
> -- 
> View this message in context: http://old.nabble.com/ValidateUserDefinedFields%3DN-doesn%27t-work-in-the--DEFAULT--Section-Of-a-settings-file-in-Quickfix-1.13.2-tp28043059p28043059.html
> Sent from the QuickFIX - User mailing list archive at Nabble.com.
>
>
> --- 
> --- 
> --- 
> ---------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Quickfix-users mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-users
>