WSDL generation

This topic defines the objects created by the WSDL Generator.

Generated Files

The default file and definition element names are shown in the table below. <Message Set> is the supplied message set name and <Definition Name> is the supplied Definition Name solicited by the wizard.

Table 1. WSDL File Naming Convention
File File Name File Extension Value of name attribute on WSDL <definitions> element
Service File (multi- or single-file format) <Message Set>Service wsdl <Definition Name>Service
Binding File <Message Set>Binding wsdl <Definition Name>Binding
Interface File <Message Set>Interface wsdl <Definition Name>
Schema File(s) Message Definition File xsd not applicable

Report File

The WSDL generator appends the result of the generation operation to a report file, listing any errors which occurred. The file name is:

<Message Set>.wsdlgen.report.txt

WSDL Content

The tables below show the element / attribute values to be set in the generated WSDL. The elements are described top-down as they appear in a conventionally ordered WSDL document. The <schema> section of the WSDL definition is not shown since this corresponds directly to the broker message definitions.

Element names are from the WSDL 1.1 namespace except where prefixed by soap: for the WSDL SOAP namespace. Operation elements occur in both the binding and portType sections, so operation is qualified as necessary – e.g. portType / operation.

The following values apply to the WSDL definition as a whole:

Table 2. WSDL objects
Element Attribute Value
definitions xmlns assign namespace prefixes.
definitions targetNamespace <Company Domain Name>/<Message Set>/definitions where <Company Domain Name> is solicited by the wizard and <Message Set> is the message set name.
message name <operation>-<role> where <operation> is the associated category name and <role> is input, output or fault
part name name of the broker message M. If Style is set to rpc, the body parts are defined using the type attribute. If not, the body parts are defined using the element attribute.
portType name <Message Set>
binding name
  • ”<Message Set>SOAP_HTTP_ Binding”
  • ”<Message Set>SOAP_JMS_ Binding”
soap:binding style From the value of Style set in the New WSDL definition wizard.

The following values apply to each individual WSDL operation (a WSDL operation is represented as a message category):

Table 3. WSDL <operation> objects
Element Attribute Value
operation name The name of the message category
soap:operation style From the value of Style set in the New WSDL definition wizard.
input, output name This optional attribute is not generated
fault name operation-fault-part
soap:body namespace
  • If Style has been set to rpc then it is the namespace of the corresponding broker message.
  • If Style has been set to document the attribute is not generated.
soap:header, soap:fault, soap:body use This is set to literal.
portType / operation parameterOrder
  • If the Style is set to document, the attribute is not generated.
  • If the Style is set to rpc, the input parts are I1..IN and output parts O1..ON. This is a space-separated list of parts omitting any explicitly identified return parts (or O1 if no return part is specified). For example:
    I1 I2 I3 O2 O3 O4

Message Set

The main result of generating WSDL from a message set is a WSDL definition for consumption by an external toolkit such as .NET. Typically, however, the broker will also need to parse the runtime SOAP messages described by that WSDL. By default the WSDL generator will leave your message set SOAP-ready for use by the MRM XML parser. This section describes what that means.

If the specified WSDL style is set to rpc:

Validation Annotation

The generated WSDL is annotated to state whether it is compliant with the Basic Profile. The WSDL generator emits the following claim on the wsdl:port element or on the highest level element for which conformance is being claimed:

<wsdl:definitions etc.
  xmlns:wsi="http://ws-i.org/schemas/conformanceClaim/"\>

  <wsdl:port name="etc" binding="etc">
      <wsdl:documentation>
        <wsi:Claim conformsTo="http://ws-i.org/profiles/basic/1.0"/>
      </wsdl:documentation>
Related concepts
Message modeling
The message model
Related tasks
Developing message models
Working with a message definition file
Working with message model objects
Generating a Web Service Definition from a message set
Related reference
Message model reference information
Message model object properties