Re: [Quickfixj-users] custom data dictionary not being used on inbound message validaiton

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

This is the corresponding data dictionary section
<field number="447" name="PartyIDSource" type="CHAR">
			<value enum="D" description="PROPRIETARY_CUSTOM_CODE" />
		</field>
		<field number="448" name="PartyID" type="STRING" />
		<field number="452" name="PartyRole" type="INT">
			<value enum="1" description="EXECUTING_FIRM" />
			<value enum="3" description="CLIENT_ID" />
			<value enum="35" description="PROVIDER" />
		</field>
		<field number="453" name="NoPartyIDs" type="NUMINGROUP" />

	After upgrading QF/J to 2.0.0 it is failing in a new way
			453=1|447=D|448=XX|452=35|
(Rejecting invalid message: quickfix.FieldException: The group 453 must set the delimiter field 448:447)

	But still failing around repeating party groups.

Thanks
Rob MacKay

-----Original Message-----
From: Robert MacKay 
Sent: Tuesday, January 9, 2018 7:12 AM
To: 'Freedman, Jon' <Jon...@br...>; 'qui...@li...' <qui...@li...>
Subject: RE: [Quickfixj-users] custom data dictionary not being used on inbound message validaiton

	The repeating group is coming from a production implementation (this work is for a test server), I have the repeating fields group working in an initiator implementation, in building this acceptor the same datadictionary file is not being read or applied by the acceptor.  The repeating groups do not match the 4.4 spec specifically because they are customized and defined in the custom datadictionary. The entire problem is that incoming messages are not being evaluated by the custom dictionary.

Thanks
Rob MacKay

-----Original Message-----
From: Freedman, Jon [mailto:Jon...@br...] 
Sent: Tuesday, January 9, 2018 12:54 AM
To: 'qui...@li...' <qui...@li...>
Cc: Robert MacKay <rm...@ne...>
Subject: RE: [Quickfixj-users] custom data dictionary not being used on inbound message validaiton

Can you anonymise the data around field 447 and include the Parties repeating groups?  I'm sure your FIX counterpart definitely didn't screw up their MiFID II changes... :)

-----Original Message-----
From: Robert MacKay via Quickfixj-users [mailto:qui...@li...] 
Sent: 08 January 2018 21:34
To: qui...@li...
Cc: Robert MacKay
Subject: [Quickfixj-users] custom data dictionary not being used on inbound message validaiton

QuickFIX/J Documentation: http://www.quickfixj.org/documentation/
QuickFIX/J Support: http://www.quickfixj.org/support/

[default]
FileStorePath=target/data/executor
ConnectionType=acceptor
StartTime=00:00:00
EndTime=00:00:00
HeartBtInt=30
SenderCompID=SNDCOMPID
TargetCompID=TRGCOMPID
UseDataDictionary=Y
DataDictionary=CUST_FIX44.xml

[session]
SenderCompID=SNDCOMPID
TargetCompID=TRGCOMPID
BeginString=FIX.4.4
SocketAcceptPort=9001
UseDataDictionary=Y
DataDictionary=CUST_FIX44.xml

Throws this error on incoming custom FIX message:

error> (Rejecting invalid message: quickfix.FieldException: 
Out of order repeating group members, field=447: 8=FIX.4.49=16535=V...

The CUST_FIX44.xml file contains definitions for the repeating groups.

The Custom DataDictionary is not being applied to message validation even though loaded and recognized. When I put in an invalid path before the xml file it throws the not found error at start, the name appears in the SessionSettings object during Application init but is not applied to validation.

Thanks
Rob MacKay

------------------------------------------------------------------------------
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

This email, the information therein and any attached materials (collectively the "Email") are intended only for the addressee(s) and may contain confidential, proprietary, copyrighted and/or privileged material. If you have received this Email in error please delete it and notify the sender immediately. This Email remains the property of Brevan Howard, which reserves the right to require its return (together with any copies or extracts thereof) at any time upon request. Any unauthorised review, retransmission, dissemination, forwarding, printing, copying or other use of this Email is prohibited. Brevan Howard may be legally required to review and retain outgoing and incoming email and produce it to regulatory authorities and others with legal rights to the information. Internet communications cannot be guaranteed to be secure or error free as information could be intercepted, changed corrupted, lost, arrive late or contain viruses. Brevan Howard accepts no liability for any errors or omissions in this Email which arise as a result of internet transmission. This Email is not an official confirmation of any transaction. Any comments or statements made herein do not necessarily reflect the views of Brevan Howard. 
This Email is not an offer to sell or solicitation of an offer to buy any security or investment. It does not constitute or contain any investment advice and is being made without regard to the recipients investment objectives, financial situation or means. Past Performance is not an indicator of future results and Brevan Howard provides no assurance that future results will be consistent with any information provided herein or attached hereto. Brevan Howard and the sender make no warranties regarding the accuracy or completeness of the information in this Email and it should not be relied upon and is subject to change without notice. Brevan Howard and its representatives, officers and employees accept no responsibility for any losses suffered as a result of reliance on the information in this Email or the reliability, accuracy, or completeness thereof.
In this Email, "Brevan Howard" means Brevan Howard Asset Management LLP ("BHAM"), Brevan Howard Inc., Brevan Howard (Israel) Ltd and their respective affiliates. BHAM is a limited liability partnership authorised and regulated by the Financial Conduct Authority of the United Kingdom and registered in England & Wales (reg. no. OC302636).