{{Quickfixn}} questions on component block concepet in quickfix

[Grant Birchmeier]

Components are implemented the same across all QuickFIX implementations.
You are mistaken in saying that QF/j does it differently.

It sounds like you are conflating two concepts: "components" and "repeating
groups".

55,48,22 are part of the "Instrument" component.  When the Instrument
component is in the top level of a message, then the order of component
fields does not matter.

*However, often the Instrument component is within a repeating group:* in
that case, the fields *do* need to be in the same sequence as specified in
the Instrument component's definition.

Is that kind of clear now?


On Tue, Mar 6, 2018 at 11:01 AM, Jie Zhu <Jie.Zhu at icbkfs.com> wrote:

> Hi,
>
>
>
> It looks the component block concept no longer exists in Quickfix/N ( and
> Quickfix C++).  For instance, an AE message, the tags inside the instrument
> component block, (e.g tag 55) will be treat the same level as other tags
> outside of the block such as 571, 572.   QuickFix J still has the component
> block concept.  Does that mean in quickfix/J , tags  55, 48, 22,et al must
> be placed together but in QuickFix/N it is not demanded?
>
> In this case, for those msg generated from quickfix/N, will they pass the
> validation of quickfix/j engine?
>
>
>
> Thanks,
>
>
>
> Jie
>
> _______________________________________________
> Quickfixn mailing list
> Quickfixn at lists.quickfixn.com
> http://lists.quickfixn.com/listinfo.cgi/quickfixn-quickfixn.com
>
>


-- 
Grant Birchmeier
*Connamara Systems, LLC*
*Made-To-Measure Trading Solutions.*
Exactly what you need. No more. No less.
http://connamara.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.quickfixn.com/pipermail/quickfixn-quickfixn.com/attachments/20180306/9a9da1b3/attachment.htm>