简体   繁体   English

我们什么时候使用FIX50sp2和FIXT11.xml?

[英]When do we use FIX50sp2 and FIXT11.xml?

I am newbie to quickfix, bit confused between quickfix versions FIX50sp2 and FIXT11. 我是quickfix的新手,quickfix版本FIX50sp2和FIXT11之间有些困惑。

When to use what? 什么时候使用什么? Also i got to know to use FIXT11.xml when using FIX 50sp2 version, why not FIX50SP2.xml ? 我也知道在使用FIX 50sp2版本时使用FIXT11.xml,为什么不使用FIX50SP2.xml?

I am trying to add a group TrdInstrmtLegGrp to my FIXT11.xml, rebuild the jar, earlier I was using quickfixj-messages-fix50sp2-2.0.0 jar but now after doing changes to FIXT11.xml and adding jar quickfixj-messages-fixt11-2.1.0-SNAPSHOT it gives error on TradeCaptureReport : 我试图将组TrdInstrmtLegGrp添加到我的FIXT11.xml中,重建该jar,之前我使用过quickfixj-messages-fix50sp2-2.0.0 jar,但是现在对FIXT11.xml进行了更改并添加了jar quickfixj-messages-fixt11-2.1.0-SNAPSHOT它在TradeCaptureReport上给出错误:

20180418-04:46:29: java.lang.VerifyError: Bad type on operand stack Exception Details: Location: quickfix/fixt11/TradeCaptureReport$NoLegs.get(Lquickfix/field/LegSide;)Lquickfix/field/LegSide; @2: invokevirtual Reason: Type 'quickfix/field/LegSide' (current frame, stack[1]) is not assignable to 'quickfix/StringField' Current Frame: bci: @2 flags: { } locals: { 'quickfix/fixt11/TradeCaptureReport$NoLegs', 'quickfix/field/LegSide' } stack: { 'quickfix/fixt11/TradeCaptureReport$NoLegs', 'quickfix/field/LegSide' } Bytecode: 0x0000000: 2a2b b600 0457 2bb0

This is how my FIXT11.xml looks as for this group in similar order of my API: 这就是我的FIXT11.xml在该组中的显示方式,与我的API相似:

<component name='InstrmtLegGrp'>
  <group name='NoLegs' required='N'>
    <field name='LegSymbol' required='N'/>
    <field name='LegSecurityID' required='N'/>
    <field name='LegSecurityIdSource1' required='N'/>
    <field name='LegSecurityDesc' required='N'/>
    <field name='LegRatioQty' required='N'/>
    <field name='LegSide' required='N'/>
  </group>
</component>

Or do I need to do the required group changes in FIX50sp2.xml? 还是我需要在FIX50sp2.xml中进行所需的组更改?

From FIX 5.0 onwards, Quickfixj introduces the concept of transport dictionary and app dictionary. 从FIX 5.0开始,Quickfixj引入了传输词典和应用程序词典的概念。 Transport dictionary will contain all transport related admin messages as Heartbeat/Logon/Logoff etc. whereas Appdictionary will contain the business messages as Quote request, trade capture etc. 运输词典将包含所有与运输相关的管理消息,如心跳/登录/注销等,而管理员将包含商业消息,如报价请求,交易捕获等。

You can check the QuickfixJ configuration TransportDataDictionary & AppDataDictionary.( https://www.quickfixj.org/usermanual/1.6.4/usage/configuration.html ) 您可以检查QuickfixJ配置TransportDataDictionary和AppDataDictionary。( https://www.quickfixj.org/usermanual/1.6.4/usage/configuration.html

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM