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, [Type content - 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.
When parsing or writing a CWF message in the MRM domain, any values specified for the message model properties Min Occurs and Max Occurs are ignored. The number of occurrences of an element is instead determined by either the Repeat Count or Repeat Reference property. However, the message validation functionality of WebSphere Business Integration Message Broker utilizes the Min Occurs and Max Occurs information.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ad10490_ |