Chapter 3 Service Endpoint Design

73

Parameters with

standard type

mapping

Implicit

binding

Web

Parameters without

SOAP request/

standard type

service

response

Parameter/

endpoint

Implicit

mapping

if (de)serializer

return value

registered

SOAP document

fragment

Java object

XML/Data

binding

Figure 3.3

Binding Parameters and Return Values with JAX RPC

Parameters for Web service method calls may be standard Java objects and

types, XML documents, or even nonstandard types. Whether you use the Java to 

WSDL approach or the WSDL to Java approach, each type of parameter must be

mapped to its XML equivalent in the SOAP message. Figure 3.3 shows how the

binding happens for various types of parameters.

3.4.1.3.1 Java Objects as Parameters

Parameters for Web service calls can be standard Java types and objects. If you use

the Java to WSDL approach, you specify the parameter types as part of the argu 

ments of the method calls of your Java interface. If you use the WSDL to Java

approach, you specify the parameter types as the 

type

 or 

element

 attributes of the

part

 element of each 

message

 in your WSDL. The type of a parameter that you use

has a significant effect on the portability and interoperability of your service. 

The platform supports the following Java data types. (Refer to the JAX RPC

specification at 

http://java.sun.com/xml/jaxrpc/

 for the equivalent WSDL

mappings for these Java data types.)