Read these notes to help your migration of message sets to WebSphere Message Broker Version 6.1.
If you are using the Message Broker Toolkit Version 5.1, replace all references in this topic to "Version 5.0" with "Version 5.1".
To migrate message sets from Version 6.0 to Version 6.1, no migration commands are necessary. The content of a Version 6.0 message set project can be read by the Message Broker Toolkit Version 6.1 and is converted automatically to Version 6.1 format when you modify and save it for the first time.
To migrate message sets from Version 5.0 to Version 6.1, no migration commands are necessary. The content of a Version 5.0 message set project can be read by the Message Broker Toolkit Version 6.1 and is converted automatically to Version 6.1 format when you modify and save it for the first time.
The following information is applicable to migration from Version 5.0 and Version 6.0.
Continue to use TDS Message Key if the message set will ever be deployed to a Version 5.0 broker, because these brokers do not support the Message Identity technique of embedded message identification.
The following information is applicable if you have migrated from Version 5.0:
<!ELEMENT e0 (e1|e2)+>appears in the output as:
<!ELEMENT e0 (e1|e2)+>The new behavior is consistent with the way that the XML physical format processes white space in all other XML constructs.
A specific example of this condition is where your message contains an embedded message and you are using either the Message Key or Message Identity technique to identify the embedded message. If the element that is providing the message key or message identity value fails to be matched with the model, the parser does not know whether to interpret its value as a message key or message identity.
Prior to Version 6.0, the parser attempted to make sense of all out-of-order Tagged Delimited groups, with a consequent reduction in performance. In Version 6.1, if this behavior is a problem, consider modeling the unordered content of the group as an embedded child group with Composition set to UnorderedSet.
A complex element or group can be identified from the bit stream if it provides a group indicator, a tag, or a data pattern, or if its child members provide a group indicator, tag, or data pattern.
Despite its name, under some circumstances members of a Tagged Delimited group do not need to provide a tag; specifically, if the member is an embedded message or is a complex element or group.