Webhosting - Serverndpoint Design for webhosting services

Designing a Service's Interaction Layer

Literal bindings cannot represent complex types, such as objects with circular

references, in a standard way.

Code Example 3.14 shows a snippet from the WSDL document illustrating

how the sample weather service specifies these bindings.

namespace="urn:WeatherWebService"/>

namespace="urn:WeatherWebService"/>

transport="http://schemas.xmlsoap.org/soap/http" />

Code Example 3.14

Specifying WSDL Bindings

It is important to keep in mind these message styles and bindings, particularly

when you design the interface using the WSDL to Java approach and when you

design the WSDL for your service. When you use the Java to WSDL approach,

you rely on the vendor provided tools to generate the WSDL for your Java inter

faces, and they can be counted on to create WS I compliant WSDL for your ser

vice. However, note that some vendors may expect you to specify certain options

to ensure the creation of a WS I compliant WSDL. For example, the J2EE 1.4

SDK from Sun Microsystems provides a

wscompile

 tool, which expects the devel

oper to use the

 f:wsi

 flag to create the WS I compliant WSDL for the service. It

is also a good idea to check the WSDL document itself to ensure that whatever

tool you use created the document correctly.

footer