Providing SOAP-Based Web Services - Java SOA - page 401

The tool also creates two WSDLs. The first is the abstract WSDL, containing only the <mes-
sages> , the <types> element (which imports all types from the generated schema), and the
<portType> element. The WSDLs are placed in the gendirectory, in accordance with the
value in the -r option in the command. The abstract WSDL, called GenCatalog.wsdlhere,
looks like this:
<definitions targetNamespace="http://ns.soacookbook.com"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:tns="http://ns.soacookbook.com"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<types>
<xsd:schema>
<xsd:import namespace="http://ns.soacookbook.com"
schemaLocation="GenCatalog_schema1.xsd"/>
</xsd:schema>
</types>
<message name="getTitle">
<part name="parameters" element="tns:getTitle"/>
</message>
<message name="getTitleResponse">
<part name="parameters" element="tns:getTitleResponse"/>
</message>
<portType name="GenCatalog">
<operation name="getTitle">
<input message="tns:getTitle"/>
<output message="tns:getTitleResponse"/>
</operation>
</portType>
</definitions>
On its own, of course, the abstract WSDL is not enough to run your service. That requires a
concrete WSDL, which the tool also generates, as follows:
<definitions targetNamespace="http://ns.com/" name="Catalog"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:tns="http://ns.com/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
<import namespace="http://ns.soacookbook.com"
location="GenCatalog.wsdl"/>
<binding name="GenCatalogPortBinding"
type="ns1:GenCatalog" xmlns:ns1="http://ns.soacookbook.com">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http"
style="document"/>
<operation name="getTitle">
<soap:operation soapAction=""/>