Considerations for mapping messages modeled in message sets
You can use the Graphical Data Mapping editor to transform XML messages that are defined in XML Schema (.xsd files). Message Set modeling in IBM® Integration Bus supports XML Schema extensions.
The Graphical
Data Mapping editor supports
both XML and text or binary messages that are modeled in IBM Integration Bus message sets, with the
following considerations:
- Message sets provide facilities for defining message composition.
When these extensions are used to redefine a wildcard in a message,
they are not shown in the message map.
The Graphical
Data Mapping editor provides
equivalent facilities for modeling choice in schema wildcards by using
the Cast function. For more information about the Cast function, see Mapping xsd:any on an input or output message.
When you create a message map or convert a message map that includes a schema wildcard from a message set with XML Schema extensions, you must manually add a Cast function from the wildcard to the required schema element.
- The message map requires the message set schema (.xsdzip file) to be deployed to run your message map. If your existing message set is used for text and binary formats only, you can deploy your message map with only a .dictionary file in the BAR file. In this case, you must modify the message set to additionally set the XMLNSC domain support option, so it is added to a BAR with both a .dictionary file and .xsdzip file. If this option is not set, a warning is displayed in the Problems view, along with a quick fix action.