There are some restrictions for messages defined using a CWF in relation to the logical model and these are discussed below.
A CWF message is always output with the elements in the sequence specified in the logical message model definition. However, you do not always have to specify ESQL that builds the elements in that sequence. The following rules for coding ESQL are given for each value for the type Composition property.
If the elements or types have default values, and you do not build the message in the correct sequence, those elements built out of sequence will contain their default values, not the values that you set. This is because elements built out of sequence are assumed to be self-defining, and for CWF these are discarded when the message is written to the bit stream.
If the elements have default values, and you do not build the message in the correct sequence, those elements built out of sequence will contain their default values, not the values that you set. This is because elements built out of sequence are assumed to be self-defining, and for CWF these are discarded when the message is written to the bit stream.
CWF is a fixed format and all elements must be present in a message. Therefore, [Content validation] is ignored. On output, all elements must be set explicitly (for example, using ESQL SET), set implicitly (using a tree copy function), or must have a default value defined.
On output of a CWF message in the MRM domain, any element, or occurrence of an element for which a value has not been set (either explicitly or implicitly) inherit the element's specified default value. If no default value has been specified then an exception is thrown.
The logical properties Min Occurs and Max Occurs specify the permitted number of occurrences of an element or group in a message. They are used when parsing and writing messages, and when validating the content of a message.
In CWF, Max Occurs occurrences are expected when parsing, and Max Occurs occurrences are output when writing with default values used for missing elements.
However this behavior is overridden if the Repeat Reference property is set which indicates that the number of occurrences is given instead by an integer element that occurs earlier in the message. In this case Max Occurs is ignored.
When validating, Min Occurs and Max Occurs are both used to check that the content of the message tree matches the model.
Lists and unions are XML-specific concepts. An element or attribute of a simple type that is a list or a union will cause a task list warning if a CWF physical format is present in the message set. The user can choose whether to make this an error, warning, or information by editing the Validation preferences. The dictionary generator will omit messages defined to contain such elements or attributes from the CWF section of the dictionary.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ad10490_ |