can QF/J work with varying field order inside groups?

4 messages

can QF/J work with varying field order inside groups?

Reply Threaded

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

(I sent a similar message to the regular C++ QuickFIX mailing list,
but I've been working with QF/J long enough to know that the C++ and
Java engines have differences. I need to know this answer for both
engines.)

Is there a configuration option that will allow fields to be
out-of-order within repeating groups?

I'm working an issue with ICE right now, and ICE support is telling me
that only the starting tag that delimits each element within a group
is important, and the order within the group is not significant.

Logically, I understand why this could be sufficient. From a FIX
perspective, however, it completely violates the spec (see FIX Version
4.4 with Errata 20030618 (the latest version), Vol 1, Section "FIX
PROTOCOL SYNTAX", sub-section "FIX 'Tag=Value' SYNTAX").

As it stands, the ICE spec's field ordering does not match reality,
and when new revisions add a field, I can't be sure where it will
appear until I see it in an actual message. I'm trying to convince
them to commit to the ordering, but so far they are not.

QuickFIX/J does not appear to permit the ordering of fields within a
repeating group to vary. I'm aware of the ValidateFieldsOutOfOrder
config option, but the description doesn't seem like it applies to
this situation.

Can QuickFIX/J be configured to work with this fudgy interpretation of
FIX? Is anyone else using QuickFIX/J with ICE?

Thanks
-Grant

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Quickfixj-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/quickfixj-users

Laurent DANESI

Re: can QF/J work with varying field order inside groups?

Reply Threaded

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

Hi Grant,

I made the ValidateFieldsOutOfOrder stuff for group parsing but perhaps there is some missing use cases.
Could you provide me or add these use cases to RepeatingGroupTest, please?

So I will be able to fix this issue.

Regards,

Laurent DANESI
Chief Architect
Smart Trade Technologies

-----Message d'origine-----
De : Grant Birchmeier [mailto:[hidden email]]
Envoyé : mercredi 23 septembre 2009 18:56
À : [hidden email]
Objet : [Quickfixj-users] can QF/J work with varying field order inside groups?

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

(I sent a similar message to the regular C++ QuickFIX mailing list,
but I've been working with QF/J long enough to know that the C++ and
Java engines have differences. I need to know this answer for both
engines.)

Is there a configuration option that will allow fields to be
out-of-order within repeating groups?

I'm working an issue with ICE right now, and ICE support is telling me
that only the starting tag that delimits each element within a group
is important, and the order within the group is not significant.

Logically, I understand why this could be sufficient. From a FIX
perspective, however, it completely violates the spec (see FIX Version
4.4 with Errata 20030618 (the latest version), Vol 1, Section "FIX
PROTOCOL SYNTAX", sub-section "FIX 'Tag=Value' SYNTAX").

As it stands, the ICE spec's field ordering does not match reality,
and when new revisions add a field, I can't be sure where it will
appear until I see it in an actual message. I'm trying to convince
them to commit to the ordering, but so far they are not.

QuickFIX/J does not appear to permit the ordering of fields within a
repeating group to vary. I'm aware of the ValidateFieldsOutOfOrder
config option, but the description doesn't seem like it applies to
this situation.

Can QuickFIX/J be configured to work with this fudgy interpretation of
FIX? Is anyone else using QuickFIX/J with ICE?

Thanks
-Grant

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Quickfixj-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/quickfixj-users

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Quickfixj-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/quickfixj-users

Grant Birchmeier

Re: can QF/J work with varying field order inside groups?

Reply Threaded

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

You're right, Laurent, your test cases show that QF/J does in fact
allow such behavior, and that the ValidateOutOfOrder setting does more
than the config web page indicates. I will remember to check the
tests first in the future.

Is it possible to append "or fields within repeating group elements
are out of order" into the parenthesized clause in the web page
description of this setting? I can submit a JIRArequest for this, if
you like.

-Grant

On Fri, Sep 25, 2009 at 5:27 AM, Laurent Danesi <[hidden email]> wrote:

> QuickFIX/J Documentation: http://www.quickfixj.org/documentation/
> QuickFIX/J Support: http://www.quickfixj.org/support/
>
>
> Hi Grant,
>
> I made the ValidateFieldsOutOfOrder stuff for group parsing but perhaps there is some missing use cases.
> Could you provide me or add these use cases to RepeatingGroupTest, please?
>
> So I will be able to fix this issue.
>
> Regards,
>
> Laurent DANESI
> Chief Architect
> Smart Trade Technologies
>
> -----Message d'origine-----
> De : Grant Birchmeier [mailto:[hidden email]]
> Envoyé : mercredi 23 septembre 2009 18:56
> À : [hidden email]
> Objet : [Quickfixj-users] can QF/J work with varying field order inside groups?
>
> QuickFIX/J Documentation: http://www.quickfixj.org/documentation/
> QuickFIX/J Support: http://www.quickfixj.org/support/
>
>
> (I sent a similar message to the regular C++ QuickFIX mailing list,
> but I've been working with QF/J long enough to know that the C++ and
> Java engines have differences. I need to know this answer for both
> engines.)
>
> Is there a configuration option that will allow fields to be
> out-of-order within repeating groups?
>
> I'm working an issue with ICE right now, and ICE support is telling me
> that only the starting tag that delimits each element within a group
> is important, and the order within the group is not significant.
>
> Logically, I understand why this could be sufficient. From a FIX
> perspective, however, it completely violates the spec (see FIX Version
> 4.4 with Errata 20030618 (the latest version), Vol 1, Section "FIX
> PROTOCOL SYNTAX", sub-section "FIX 'Tag=Value' SYNTAX").
>
> As it stands, the ICE spec's field ordering does not match reality,
> and when new revisions add a field, I can't be sure where it will
> appear until I see it in an actual message. I'm trying to convince
> them to commit to the ordering, but so far they are not.
>
> QuickFIX/J does not appear to permit the ordering of fields within a
> repeating group to vary. I'm aware of the ValidateFieldsOutOfOrder
> config option, but the description doesn't seem like it applies to
> this situation.
>
> Can QuickFIX/J be configured to work with this fudgy interpretation of
> FIX? Is anyone else using QuickFIX/J with ICE?
>
> Thanks
> -Grant
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9-12, 2009. Register now!
> http://p.sf.net/sfu/devconf
> _______________________________________________
> Quickfixj-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/quickfixj-users
>
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9-12, 2009. Register now!
> http://p.sf.net/sfu/devconf
> _______________________________________________
> Quickfixj-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/quickfixj-users
>

Laurent DANESI

Re: can QF/J work with varying field order inside groups?

Reply Threaded

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

Of course, I've just updated the configuration page.

Laurent

-----Message d'origine-----
De : Grant Birchmeier [mailto:[hidden email]]
Envoyé : mercredi 30 septembre 2009 02:03
À : [hidden email]
Objet : Re: [Quickfixj-users] can QF/J work with varying field order inside groups?

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

You're right, Laurent, your test cases show that QF/J does in fact
allow such behavior, and that the ValidateOutOfOrder setting does more
than the config web page indicates. I will remember to check the
tests first in the future.

Is it possible to append "or fields within repeating group elements
are out of order" into the parenthesized clause in the web page
description of this setting? I can submit a JIRArequest for this, if
you like.

-Grant

On Fri, Sep 25, 2009 at 5:27 AM, Laurent Danesi <[hidden email]> wrote:

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Quickfixj-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/quickfixj-users

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Quickfixj-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/quickfixj-users