WebSphere Message Brokers
File: ad10360_
Writer: Terry Cowling

Concept topic

This build: July 31, 2007 21:23:47

Message model objects: groups

A group is a list of elements which defines how those elements can appear in a message.

Groups can be ordered (sequence) unordered (all) or selective (choice). Groups define the composition and content validation of a set of type members.

What are groups for?

Groups can be used for any of the following purposes:

Contents of a group

Groups can contain complex elements, simple elements, wildcard elements and groups.

By combining these components, the structure of any message can be modeled. Wildcard elements can be included to allow unmodeled elements to appear, thus making the message model robust and flexible.

Global and local groups

Groups can be global or local.

A global group can be used in more than one place in the message model. It represents a structure which appears in more than one place in the message model. A global group must be given a unique name by which it can be referenced.

A local group is defined in one position within one group, and is not available for reuse elsewhere in the message model. Local groups do not need to be named.

Composition

In XML Schema, a group can have its composition set to sequence, all or choice.

The message model also allows other compositions, in order to remain compatible with earlier versions of the product. For further information, see Schema extensions in the message model.

Content validation

The Content validation property is only applied when the domain is MRM or IDOC, and when validation is enabled.

Content validation determines how strictly the content of the group should be validated. See MRM content validation for further details.

Possible values of the Content validation property are:
Closed
The contents of the group are validated strictly against the model.
Open Defined
Elements that are declared within the same message set can appear as children of the group, even if they are not modeled.
Open
No validation is performed.

The Content validation property does not affect validation in the XMLNSC domain.

Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:23:47

ad10360_ This topic's URL is: