Java Reference
In-Depth Information
<operation name="sayHello" parameterOrder="arg0">
<input message="tns:sayHello"></input>
<output message="tns:sayHelloResponse"></output>
</operation>
</portType>
<binding name="HelloWSPortBinding" type="tns:Hello">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/
soap/http">
</soap:binding>
<operation name="sayHello">
<soap:operation soapAction=""></soap:operation>
<input>
<soap:body use="literal" namespace="http://ch03.soacookbook.com/
"></soap:body>
</input>
<output>
<soap:body use="literal" namespace="http://ch03.soacookbook.com/
"></soap:body>
</output>
</operation>
</binding>
<service name="HelloWSService">
<port name="HelloWSPort" binding="tns:HelloWSPortBinding">
<soap:address location="http://localhost:9999/
hello"></soap:address>
</port>
</service>
</definitions>
There are a few things to notice about the WSDL published by the endpoint. Let's look at
them to gain a better understanding of how this all works.
Types
This Types section of the WSDL is empty. Types is where a WSDL either imports or locally
defines the XML schema types that the messages your web service exchanges will use. The
reason this section is empty is that the messages defined by this web service use only strings,
which are defined as a simple type in XML Schema—all web services will be able to use them
out of the box. So it's not necessary to put anything there.
Frequently, WSDLs will define a Types section that points to an external schema. In your We-
bLogic service created in
Creating and Deploying a Service to WebLogic
,
the WSDL indic-
ates the location of a schema, generated by the server at deploy time, that defines the types the
messages will use:
