Re: [Quickfixj-users] [Initiator] Multileg field 555 changed, field 654 (and the entire leg) dropped.

[philip <ph...@wh...>]

If the message does not match the dictionary, the parsed message will be 
broken regardless of validation settings. If you have repeating groups 
you need a dictionary that can parse those.

In such a scenario, message.getException() will be non-null and should 
give you the reason why the message was dropped.

In the latest code the actual raw message is available as: 
message.toRawString() - although I'm not sure if this has been released 
yet.

- Philip Witehouse

On 2018-08-10 10:15, ToonXW wrote:
> QuickFIX/J Documentation: http://www.quickfixj.org/documentation/
> QuickFIX/J Support: http://www.quickfixj.org/support/
> 
> 
> Hi,
> 
> Upon receiving a multileg TradeCaptureReport (MsgType=AE) where field 
> 555 is
> set to 2 and comes with two fields 654 followed by the respective leg 
> tags;
> but upon retrieving the message via fromApp it is seen that field 555's
> value has been switched from 2 to 1 and all legs were dropped, i.e. tag 
> 654s
> disappear along with the rest of the tags. Please advise on why this is
> happening as the goal is to *retain the original message obtained and 
> not
> have any processing done to it* - most validation have been turned off.
> 
> Config:
>                 UseDataDictionary=Y
>                 ValidateFieldsOutOfOrder=N
>                 ValidateFieldsHaveValues=N
>                 ValidateUserDefinedFields=N
>                 ValidateIncomingMessage=N
>                 AllowUnknownMsgFields=Y
> 
> Many thanks.
> 
> 
> 
> --
> Sent from: http://quickfix-j.364392.n2.nabble.com/
> 
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Quickfixj-users mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfixj-users