|
From: Steve B. <st...@te...> - 2006-11-08 01:28:44
|
> The reason I do not want to use NewOrderSingle.NoPartyIDs is that my order
> object can be either a NewOrderSingle or NewOrderMultileg. Not sure if I
> can add a NewOrderSingle.NoPartyIDs object to a NewOrderMultileg object?
> Could you clarify? Just wonder why there is not an abstract class sitting
> on the top like GeneralOrder which can enclose some common fields or
> classes like NoPartyIDs?
The messages correspond directly to the FIX specification.
You don't necessarily need a new build. Have you tried using the
Group(int field, int delim, int[] order) constructor in 1.0.4?
The only change I made was to make Group(field, delim) call
Group(field, delim, new int[] { delim }). Better yet, you'll
be safer if you include all the tags in the integer array in
the correct order. However, like Oren said, many FIX engines
will not enforce the order of the non-delimeter tags.
Steve
|