|
From: Robert N. <rob...@gm...> - 2020-09-15 16:50:25
|
I have RejectInvalidMessage=N in order to avoid a vendor adding new tags or new enum values breaking the processing of a message on my side if it’s a tag that I don’t care about. However, it’s evident that in earlier releases of quickfixj that this doesn’t insulate you from this kind of event because it will effectively stop parsing the message as soon as it finds something it doesn’t like. Even if it’s just going to warn about it. If somebody adds a new repeating group tag in the message that my FIX dictionary knows nothing about then I’ll still process the message but it’s extremely unlikely that it will parse the content after the new repeating group therefore resulting in a partially parsed message being processed. Q. is this the correct understanding and do all quickfixj releases work this way? If not all releases work this way when did this behavior change such that it makes a best effort at parsing the message? What settings allow me to still be able to fully parse the message ignoring any new content that doesn’t align with my dictionary but still end up with a message equivalent to that which didn’t have the new repeating group tags? |