LibraryToggle FramesPrintFeedback

To generate a SOAP 1.1 binding using wsdl2soap use the following command:

wsdl2soap {-i port-type-name} [-b binding-name] [-d output-directory] [-o output-file] [-n soap-body-namespace] [-style (document/rpc)] [-use (literal/encoded)] [-v] [[-verbose] | [-quiet]] wsdlurl

The command has the following options:

-i port-type-name

Specifies the portType element for which a binding is generated.

wsdlurlThe path and name of the WSDL file containing the portType element definition.

The tool has the following optional arguments:

-b binding-nameSpecifies the name of the generated SOAP binding.
-d output-directorySpecifies the directory to place the generated WSDL file.
-o output-fileSpecifies the name of the generated WSDL file.
-n soap-body-namespaceSpecifies the SOAP body namespace when the style is RPC.
-style (document/rpc)Specifies the encoding style (document or RPC) to use in the SOAP binding. The default is document.
-use (literal/encoded)Specifies the binding use (encoded or literal) to use in the SOAP binding. The default is literal.
-vDisplays the version number for the tool.
-verboseDisplays comments during the code generation process.
-quietSuppresses comments during the code generation process.

The -i port-type-name and wsdlurl arguments are required. If the -style rpc argument is specified, the -n soap-body-namspace argument is also required. All other arguments are optional and may be listed in any order.


wsdl2soap does not support the generation of document/encoded SOAP bindings.

For more information see wsdl2soap in Web Service Tool Reference.

If your system has an interface that takes orders and offers a single operation to process the orders it is defined in a WSDL fragment similar to the one shown in Example 2.1.

The SOAP binding generated for orderWidgets is shown in Example 2.2.

This binding specifies that messages are sent using the document/literal message style.

Comments powered by Disqus