[QFJ-308] Fieldorder cannot be changed for NewOrderSingle, NewOrderMultiLeg, NewOrderCross Created: 28/Apr/08 Updated: 17/Jun/08 |
|
| Status: | Open |
| Project: | QuickFIX/J |
| Component/s: | Message Generation |
| Affects Version/s: | 1.3.1 |
| Fix Version/s: | Future Releases |
| Type: | Improvement | Priority: | Default |
| Reporter: | Peter Reinhardt | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Description |
|
The class NewOrderSingle does not allow to define a custom fieldorder, e.g. the constructor from the superclass Message(int[] fieldOrder) is not exposed. I have a couple of extra fields my company uses, and currently I cannot change the order for these fields. |
| Comments |
| Comment by Steve Bate [ 03/May/08 ] |
|
Have you considered creating a custom NewOrderSingle class with your company's field ordering and support for extra fields? You'd still need to add extra fields to the data dictionary for validation purposes. You can also generate all messages to have data dictionary-defined ordering. See the documentation on how to do that. |
| Comment by Peter Reinhardt [ 06/May/08 ] |
|
Yes, that's possible. I just have to make a copy of the NewOrderSingle class (and some of the other Order classes like NewOrderMultileg) class to support the additon of 2 custom fields. So I have to duplicate 99% of the code of the NewOrderSingle class to have custom ordering. I think it would be much easier to expose the constructor. |