Extend API to support adding field by dataType, tagNum and value. #3
Description
use the fix tag number instead of a tag name, it becomes very confusing switching back and forth. This object oriented idea of taking a fix tag number, change it to a name, then use the name everywhere, then finally output a fix tag number again, sounds good in OO theory but is a pain. It would be simpler have the api only based on fix tag numbers.
comment by Robert J Wolf.
API does not actually use tag names (strings).
It uses tag numbers (int) and enums (fixio.fixprotocol.FieldType), generated from FIX 5.0 SP2 specification.
It is possible to use either int or enum in methods like "message.add(tag, value)". Use numbers for non-standard (custom) tags.
It should be possible to add new field to FixMessageBuilder by specifying dataType, tagNum and value, without lookup a FieldType by tagNum.
I have no idea how to get rid of this lookup when parsing message from stream, because there is no information what kind of field should be added to FixMessage.