| Table of Contents |
|---|
...
- self-sufficient dictionary which describes the FIX protocol;additional dictionary which describes changes to be applied to another existing dictionary.
| Info |
|---|
FIX Antenna JAVA dictionaries have the same format as FIX Antenna C++/.NET dictionaries |
- additional dictionary which describes changes to be applied to another existing dictionary.
| Warning |
|---|
FIX Antenna JAVA does not support additional dictionary. |
...
| Structure | Description | |||
|---|---|---|---|---|
| <fixdics> | Root tag of the additional dictionary. | |||
| <update> | Dictionary update operation. Can be zero or one <update> element. | |||
<fixdic> | Dictionary to be updated. Can be zero or more <fixdic> elements. | |||
| @id | ID of the additional dictionary. | |||
| @parent_id | ID of the original dictionary additional dictionary based on. Valid values are:
| |||
| @fixversion | FIX version additional dictionary based on. | |||
| @title | The name of the additional dictionary. | |||
| @version | Additional dictionary version. | |||
| @date | Date of the last additional dictionary update. | |||
| ... | <typedef>/<valblockdef>/<fielddef>/<blockdef>/<msgdef> to be added/updated. The structure of listed elements is the same as described in standalone dictionary structure. | |||
| </fixdic> | - | |||
| </update> | - | |||
| </fixdic> | - | |||
Please see the article How to use custom dictionaries for the cases of additional dictionaries usage.
| Info |
|---|
There is no way to remove an elements from the base FIX dictionary |
How to manage list of dictionaries in FIXAntenna based applications
...