You can populate a message set with message definitions by importing XML Schema files, by using the New Message Definition File From XML Schema file wizard, the Start from WSDL and/or XSD files quick start wizard.
Each XML Schema file that you import results in a new message definition file within the message set. The root name of the message definition file defaults to the root name of the XML Schema file, but the New Message Definition File From XML Schema file wizard allows you to choose a different root file name.
If the message definition file already exists, you must have enabled overwriting to occur for the import to proceed, in which case the existing content is deleted and re-created.
The namespace to which the message definition file created belongs depends on whether namespaces have been enabled for the message set.
A report file is created during the import operation. This is located by default in the log folder of the message set. By default it takes the name of the message definition file, with .report.txt appended.
When you import by using the New Message Definition File From XML Schema file wizard, you can specify which of the global elements or global complex types within the imported XML Schema file are to be messages within the message definition file.
You can import only one XML Schema file with each import operation. If your XML Schema file references other XML Schema files, with import or include elements, these XML Schema files must be imported into the same message set by using a separate import operation.
In addition to creating logical information, the import can also create physical information. If the message set contains any XML wire format physical formats, the physical format properties for all XML Wire Format layers is populated. If the message set does not contain any XML physical formats, only logical information is created.
MRM CWF and TDS physical format properties are not populated and so take default values.
If you have one or more CWF or TDS layers, the import can cause entries in the task list, warning you that certain CWF or TDS properties must be set if the XML structures you have imported are to appear in a CWF or TDS message.
If the CWF or TDS physical formats are not applicable to your XML structures, you can ignore these task list entries because they are just warnings, they do not prevent your model being generated in another form; for example, as a message dictionary.
For details about XML Schema, see XML Schema
Part 0: Primer
on the
World Wide Web Consortium (W3C) website.