[QFJ-159] Add msgTypeName -> msgType mapping to DataDictionary Created: 29/Mar/07 Updated: 12/Apr/07 Resolved: 30/Mar/07 |
|
Status: | Closed |
Project: | QuickFIX/J |
Component/s: | Engine |
Affects Version/s: | 1.0.5 |
Fix Version/s: | 1.1.0 |
Type: | Improvement | Priority: | Major |
Reporter: | Naresh Bhatia | Assignee: | Steve Bate |
Resolution: | Fixed | Votes: | 0 |
Labels: | None | ||
Environment: |
Windows, Solaris |
Description |
I need msgTypeName -> msgType mappings in the DataDictionary class. Here's my use case: I have a requirement to be able to change the message metadata dynamically. For example, if a custom field tag value is wrong in a running system, then I should be able to correct it without bouncing the system. Hence message creation and parsing should be completely metadata driven (no hard coding of msgTypes and field tag values is allowed). Looking at the DataDictionary interface, I think message parsing can be completely driven by it, but I am not sure if message creation can be driven by the same metadata. For creating a message, I need to set the MsgTpe. However given a message name (e.g. "NewOrderSingle"), I don't see any way to get the msgType (e.g. "D") . What is needed is a simple method on the DataDictionary that returns a msgType given the message name. For example, String getMsgType(String msgName); Thus dd.getMsgType("NewOrderSingle") will return "D". Is this a convincing use case to add the method to DataDictionary API? Is there another way to solve the issue? |
Comments |
Comment by Steve Bate [ 30/Mar/07 ] |
I've committed the changes to the trunk (to be released as 1.1 soon). If you need to use the updated DataDictionary in 1.0.5, it should work, but I can't guarantee it. |
Comment by Naresh Bhatia [ 07/Apr/07 ] |
Thanks Steve. I have temprorily hard coded the msgType in my code. I will switch over to your new API as soon as 1.1 is released. |