writeSOAP: Write SOAP message elements directly to connection
In sckott/SSOAP: Client-side SOAP access for S

Description Usage Arguments Value Note Author(s) References See Also

These functions write the different parts of the SOAP request directly to an S connection. This means that they generate their content for the connection in order.

writeSOAPBody(method, ..., xmlns = NULL, con, .types = NULL,
              .soapArgs = list(), .literal = FALSE,
              .header = NULL, .elementFormQualified = FALSE)
writeSOAPEnvelope(con, nameSpaces = SOAPNameSpaces())

writeSOAPMessage(con, nameSpaces, method, ..., .types = NULL,
                    xmlns = NULL, .soapArgs = list(), .literal = FALSE,
                     .soapHeader = NULL, .elementFormQualified = FALSE)

`method`	the name of the SOAP method to be invoked
`...`	For `writeSOAPBody` and `writeSOAPMessage`, these are the name-value arguments for the SOAP method being called.
`.soapArgs`	an alternative mechanism for passing arguments to the .SOAP call. This is a `list` of named or unnamed values which is used as the arguments for the SOAP method invocation.
`xmlns`	the namespace given either as a simple string or as a named character vector of namespace URIs and local names. (Currently only one namespace is used). This is used for the top-level element of the node within the SOAP Body, corresponding to the actual request.
`con`	the connection object on which to write the HTTP and SOAP content
`.types`	a list parallelling the arguments to the SOAP method (i.e. ... or `.soapArgs`) that specify the expected/required type of the individual arguments. This information is typically constructed from the WSDL (Web Services Description Language) if that is available. Otherwise, this can be an empty list in which case no constraints are placed on the arguments and the values are used as-is.
`nameSpaces`	a named character vector giving the namespace identifier and URI pairs. These are added as attributes in the SOAP `Body` element of the generated XML.
`.literal`	a logical value indicating whether to use the literal format of the encoding for the seralization of objects.
`.header`	a character string (or `NULL` that is written as part of the SOAP header (not the HTTP header), before any other output, i.e. before the `<SOAP-ENV:Body>` is emitted. This is passed as the first argument to `writeSOAPHeader`.
`.soapHeader`	a string, an XML node or a function that can be optionally specified to add content to the SOAP message as the header of the envelope. This is used in some Web services to provide transaction information such as a authentication and security details. See the eBaySvc.wsdl for an example. If this is a function, it is called with the value of `con` as the only argument. One might use a closure to include the "private" and auxiliary information.
`.elementFormQualified`	a logical value. If this is `FALSE`, only the XML element identifying the method call in the Body of the SOAP request uses the target namespace. The XML nodes representing the arguments in the method call do not use this namespace but are global. Alternatively, if this is `TRUE`, the target namespace of the schema is defined as the default name space on the XML element for the method call and so is inherited by the elements for the parameters.

For each function, the return value is irrelevant. It is the side-effect of writing to the connection that is used for.

A different approach is to create the XML “payload” first as a string (by creating it as an XML tree and then serializing that to a buffer). This allows one to add the Content-Length to the HTTP header.

Duncan Temple Lang <duncan@wald.ucdavis.edu>

http://www.w3.org/TR/SOAP/ http://www.omegahat.org/SSOAP, http://www.omegahat.org/bugs.

.SOAP

sckott/SSOAP documentation built on Sept. 16, 2020, 5:49 p.m.