268

Similarly, the architects standardize on the WSDL to use for invoices when

fulfilling an order. Suppliers, such as airlines, hotels, and activity providers, use

these schemas and WSDL descriptions when interacting with the adventure

builder enterprise. Code Example 6.2 shows the WSDL for the Web service end 

point to which the suppliers send their invoices. 

The WSDL shown in Code Example 6.2 provides a single operation,

submitDocument

, which has a single 

xsd:anyType

 parameter representing the

invoice XML document and which returns a single string value indicating a con 

firmation. The use of 

xsd:anyType

 enables an endpoint to receive multiple types

of invoice documents with one method. See  Exchanging XML Documents  on

page 107. A WSDL document normally begins with the type definitions that it

uses, such as the exception type 

InvalidDocumentException

. (For brevity, the

code sample omits these type definitions.) The WSDL code then describes the

SOAP messages used in the SOAP request and reply calls that correspond to the

submitDocument

 method. It also describes a WSDL port corresponding to the

JAX RPC interface for receiving invoices, plus it binds the port to the HTTP pro 

tocol and indicates the RPC literal binding. Finally, the WSDL code defines the

name of the service and the URL at which the service is available. (For a more

detailed explanation of a WSDL document, see  Web Services Description Lan 

guage  on page 36.)

...