Advanced Queuing - Oracle

SOAP Method Invocation
The Internet Data Access Presentation (IDAP)
A method invocation is performed by creating the request header and body and
processing the returned response header and body. The request and response
headers can consist of standard transport protocol-specific and extended headers.
In the case of SMTP (e-mail), the method invocation can be done by the filter
interface of the e-mail server, which invokes a Java method with the
e-mail-message-body as argument. This results in remote invocation of the POST
method on the AQ servlet. The response is e-mailed directly to the recipient
specified in the reply of the message. The response header can contain
SMTP-protocol-related headers also.
HTTP Headers
The POST method within the HTTP request header performs the SOAP method
invocation. The request should include the header SOAPMethodName, whose value
indicates the method to be invoked on the target. The value consists of a URI
followed by a "#", followed by a method name (which must not include the "#"
character), as follows:
SOAPMethodName: http://ns.oracle.com/AQ/schemas/access#AQXmlSend
The URI used for the interface must match the implied or specified namespace
qualification of the method name element in the SOAP:Body part of the payload.
Method Invocation Body
SOAP method invocation consists of a method request and optionally a method
response. The SOAP method request and method response are an HTTP request
and response, respectively, whose content is an XML document that consists of the
root and mandatory body elements. This XML document is referred to as the SOAP
payload in the rest of this chapter.
The SOAP payload is defined as follows:
The SOAP root element is the top element in the XML tree.
The SOAP payload headers contain additional information that must travel
with the request.
The method request is represented as an XML element with additional elements
for parameters. It is the first child of the SOAP:Body element. This request can
be one of the AQ XML client requests described in the next section.
Internet Access to Advanced Queuing 17-5