A multipart message contains one or more other messages within its structure. The contained message is sometimes referred to as an embedded message.
A multipart message must contain a group or a complex type with its Composition property set to Message.
This group or complex type can contain
a list of references
to messages which
are allowed to
appear at that location
in the message structure
, or it may be empty , permitting any
message to appear
. When a message is parsed, only one message can appear
in that position as an embedded message.
An embedded message can be from the same message set as the multipart
message, or it can be from a different message set altogether.
A common use of multipart messages is to define an outer message with a fixed structure. This outer message is called the message envelope. Within the message envelope a group or complex type is included, as described above.
When a multipart message is parsed, the parser needs to be able to identify
the embedded message (it could be any of the messages referenced by the group
or complex type), or it could be a message not referenced by
the group or complex type, perhaps from a different message set). This is
achieved using one of two techniques, Message Identity or Message Path.
.
When a multipart message is received or generated by a broker, all embedded
messages must be of the same physical format as the outermost message and
have the same character set and encoding
.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ad00760_ |