Message Sets: Generating a WSDL definition from a message set
To ensure the highest interoperability of your web services, use the document style of WSDL whenever possible. If rpc style WSDL is necessary, use literal encoding.
Before you begin
Before you start you must already have completed the following tasks:
Replace any deprecated constructs before generating WSDL representations of your message models.
About this task
To generate a WSDL definition:
Procedure
Results
On completion of the Generate WSDL wizard, you have generated a WSDL definition. The file extension for WSDL files is .wsdl, and the file extension for any imported schema files in multi-file mode (where the WSDL definition is split over a number of files) is .xsd.
This following is an example of the WSDL that is generated for a JMS binding:
<wsdl:service name='HTTP'>
<wsdl:port binding='tns:JMSSoapBinding' name='HTTP'>
<wsdlsoap:address
location='jms:/queue?destination=jms/MyQueue&
connectionFactory=jms/MyCF&
priority=5&
targetService=GetQuote'/>
</wsdl:port>
</wsdl:service>
Note: The various parts of the location string are broken
over separate lines for clarity, but are generated as a continuous
string without additional white space.