{{Quickfixn}} Nested group leads to GroupDelimiterTagException "Group 12345's first entry does not start with delimiter 0"

[Grant Birchmeier]

The conversation for this post has moved to
https://github.com/connamara/quickfixn/pull/513

On Mon, Feb 18, 2019 at 12:15 AM オイゲン デュック <eugen at tworks.co.jp> wrote:

> Hi
>
> I've stripped down a more complex example of a custom fix message that
> QuickFix/n will throw an exception on when parsing:
>
> <message name="Example" msgtype="EX" msgcat="app">
>    <group name="NoEx1" required="Y">
>      <group name="NoEx1A" required="Y">
>        <field name="Symbol" required="Y"/>
>      </group>
>    </group>
> </message>
>
> I can create messages using that defintion like this:
>
> var exampleMsg = new Example();
> var ex1Grp = new Example.NoEx1Group();
> var ex2Grp = new Example.NoEx1Group.NoEx1AGroup { Symbol = "ABC" };
> ex1Grp.AddGroup(ex2Grp);
> exampleMsg.AddGroup(ex1Grp);
>
> which will be serialized to something like
>
> 8=FIXT.1.1 9=29 35=EX 12345=1 12346=1 55=ABC 10=223
>
> However, when parsing the message, I get the aforementioned exception:
>
> GroupDelimiterTagException  "Group 12345's first entry does not start
> with delimiter 0"
>
> If I add some non-group field to "NoEx1" and set it, then the message
> will be parsed. But unfortunately, that's not conforming to the custom
> fix spec.
>
> Is there a way to work around this "group with a group as the first item"?
> _______________________________________________
> 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/20190218/a84ea14b/attachment.htm>