لطفا منتظر باشید ...
Using SOAP and the Oracle XDK
XML Services included in Oracle XDK 10g uses the Oracle SOAP implementation that is part of Oracle AS 10g version 9.0.4 as its SOAP run-time engine, which is part of the Oracle XDK. The Oracle SOAP implementation is based on the Apache SOAP implementation and is SOAP 1.1. Therefore, the XML Services are SOAP services and can be invoked by any SOAP-compatible client, the description of which follows.
SOAP Client
The SOAP client must perform the following steps:
Gather all parameters that are needed to invoke a service.
Create a SOAP service request message. This is an XML message, built according to the SOAP protocol, that contains all of the values of all input parameters encoded in XML. This process is called serialization of the parameters.
Submit the request to a SOAP server using some transport protocol that is supported by the SOAP server.
Receive a SOAP response message.
Determine the success or failure of the request by handling the SOAP Fault element.
Convert the returned parameter from XML to a native data type. This process is called deserialization.
Use the result as needed.To enable you to avoid dealing with XML and SOAP at a very low level, a number of SOAP clients are available that will do most of this work for you. To facilitate easy application development and to insulate the application developers from all details of using SOAP, XML Services includes a SOAP client API. This API provides an easy way to invoke SOAP services from the XML Services framework. The XML Services SOAP client API supports a synchronous invocation model for requests and responses.
SOAP Server
Any SOAP server follows the following general steps while executing a SOAP service request:
The server receives the service request.
After parsing the XML request, the server must decide whether to execute the message or reject it.
If the message is to be executed, the server finds out if the service that is requested exists.
The server converts all input parameters from XML into data types that the service understands.
The server invokes the service.
The server converts the return parameter to XML and generates a SOAP response message.
The server sends the response message back to the caller.
SOAP Handlers
A SOAP handler is simply a mechanism that is used to intercept the SOAP message to do either pre- or post-processing as indicated by the SOAP request or response. These can be used on the client or server side, or both, and can add additional features to XML services, such as security, error handling, and so forth. For the Java language binding, all SOAP handlers live in the package namespace user.soap.handlers hierarchy.An example of such a handler would be the following in a SOAP XML configuration file:
<osc:handlers>
<osc:handler name="book" class="opress.soap.handlers.book.BookLogger">
<osc:option name="BookLogDirectory"
value="/private1/opress/app/product/tv02/soap/webapps/soap/WEB-INF"/>
<osc:option name="filter" value="(!(host=localhost))"/>
</osc:handler>
</osc:handlers>
<osc:requestHandlers names="book"/>
<osc:responseHandlers names="book"/>
<osc:errorHandlers names="book"/>
