EJB, Spring Remoting, and Web Services - Spring Enterprise Recipes: A Problem Solution Approach - page 233

<?xml version="1.0" encoding="UTF-8" ?>
<wsdl:definitions ...
targetNamespace=" http://springenterpriserecipes.apress.com/weather/schemas ">
<wsdl:types>
<!-- Copied from the XSD file -->
...
</wsdl:types>
<wsdl:message name="GetTemperaturesResponse">
<wsdl:part element="schema:GetTemperaturesResponse"
name="GetTemperaturesResponse">
</wsdl:part>
</wsdl:message>
<wsdl:message name="GetTemperaturesRequest">
<wsdl:part element="schema:GetTemperaturesRequest"
name="GetTemperaturesRequest">
</wsdl:part>
</wsdl:message>
<wsdl:portType name=" Weather">
<wsdl:operation name=" GetTemperatures">
<wsdl:input message=" schema:GetTemperaturesRequest"
name="GetTemperaturesRequest">
</wsdl:input>
<wsdl:output message=" schema:GetTemperaturesResponse"
name="GetTemperaturesResponse">
</wsdl:output>
</wsdl:operation>
</wsdl:portType>
...
<wsdl:service name="WeatherService">
<wsdl:port binding="schema:WeatherBinding" name="WeatherPort">
<soap:address
location=" http://localhost:8080/weather/services" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
In the Weather port type, a GetTemperatures operation is defined, whose name is derived from the
prefix of the input and output messages (i.e., <GetTemperaturesRequest> and <GetTemperaturesResponse> ).
The definitions of these two elements are included in the <wsdl:types> part, as defined in the data contract.
5-10. Implementing Web Services Using Spring-WS
Problem
Once you have defined the contract for your web service, you can start implementing the service itself
according to this contract. You want to use Spring-WS to implement this service.