Non-bound WSDL

When developing a client application following best practices, we can develop against a WSDL document containing only a port type definition, and no specific bindings or port addresses. Such a WSDL document is known as a non-bound WSDL document.

The details of the specific deployment of the web service, the bindings and the port addresses should be specified at deployment time through a bound WSDL, or by specifying the retargeted binding namespace and endpoint address either when the client application is deployed or afterward through administration.

The current WSDL specification requires there to be a binding and port element to link from a service element to a port type, so these elements do exist in a non-bound WSDL document. However they contain no extensibility elements to define a specific deployment of the service.

Here is an example of a non-bound WSDL document:

 <definitions targetNamespace="http://www.ibm.com/websphere/sib/webservices/Service"
                     xmlns:tns = "http://www.ibm.com/websphere/sib/webservices/Service">
   <message name="GetQuoteInput">
     <part name="symbol type="xsd:string"/>
   </message>
   <message name="GetQuoteOutput">
     <part name="value" type="xsd:float"/>
   </message>
     <portType name="StockQuote">
     <operation name="getQuote">
       <input message="tns:GetQuoteInput"/>
       <output message="tns:GetQuoteOutput"/>
     </operation>
   </portType>
     <binding name="StockQuoteBinding" type="StockQuote"/>
     <operation name="getQuote"/>
   </binding>
   <service name="StockQuote">
     <port name="StockQuotePort" binding="StockQuoteBinding" />
   </service>
 </definitions>"

At deployment time a bound WSDL usually replaces the one used for development. Following this replacement, the port bindings and addresses can be retargeted. The non-bound WSDL can remain if you are specifying a retargeted binding namespace and endpoint address for the empty port.

When you modify an inbound service configuration, we can export to a compressed file the non-bound WSDL for bus destinations that are enabled for web service access. The exported non-bound WSDL document can then be used to develop web service requester applications that send web service messages through the messaging destination.

Alternatively, we can use the java2wsdl tool to generate a non-bound WSDL. The java2wsdl tool has a value of "none" for the -bindingTypes option. When specified this value, the tool produces a non-bound version of the WSDL document to represent the Java object.

Related

Publish WSDL files to ZIP file [Settings]