Web Services - Java Data Mining: Strategy, Standard, and Practice - page 285

JAX-RPC Service Requester JAX-RPC Service Provider

1) JAX-RPC client
invokes service
provider operation

3) Receive SOAP request
message and convert the
call to Java service call

H
T
T
P

4) Perform Java operation
and return the response
object

2) Convert call to XML-
based SOAP request
message

6) Receive SOAP
response message and
convert it to Java object

5) Convert response to
XML based SOAP
response message

HTTP

Figure 11-10 JAX-RPC runtime.

converts this call to the XML-based SOAP protocol-compliant
request message and sends this message to the remote service pro-
vider using HTTP protocol as shown in steps 1 and 2. Once the service
provider receives this message, it converts the SOAP request message
to the appropriate Java service method call as shown in step 3. After
the completion of the Java method execution by the service provider,
the method's return parameter is converted to the appropriate SOAP
response message and sent to the requester over HTTP protocol, as
shown in steps 4 and 5 in Figure 11-10. The service requester receives
the response message and converts it to the appropriate Java object
that can be used by the Java client program as a regular method
return parameter. For more details on JAX-RPC, refer to [Haefel
2003] and [JAX-RPC 2006].

11.4.2 Building JDMWS Using JAX-RPC

This section describes how to use JAX-RPC to build a JDM Web
service that can be portable across multiple JDM vendor implemen-
tations. The JDM API defines Java interfaces; hence there are no
data members defined in the API. As a result, it is not feasible to
directly map the JAX-RPC from the JDM standard API to JDM
Schema and WSDL definitions. However, as the JDM Schema maps
to the JDM API object structure, by using JAX-RPC tools one can