writeSOAPBody             package:SSOAP             R Documentation

_W_r_i_t_e _S_O_A_P _m_e_s_s_a_g_e _e_l_e_m_e_n_t_s _d_i_r_e_c_t_l_y _t_o _c_o_n_n_e_c_t_i_o_n

_D_e_s_c_r_i_p_t_i_o_n:

     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.

_U_s_a_g_e:

     writeSOAPBody(method, ..., xmlns = NULL, con, .types = .types)
     writeSOAPEnvelope(con, nameSpaces = SOAPNameSpaces)
     writeSOAPMessage(con, nameSpaces, method, ..., .types = NULL, xmlns = NULL)
     writeSOAPHeader(url, host, action, con, ...)

_A_r_g_u_m_e_n_t_s:

  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. For
          'writeSOAPHeader', these is a collection of name-value
          strings that are added to the HTTP header

   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

     url: the name of the file within the host, without the leading `/'

    host: the name of the host for the SOAP server, e.g.
          'www.omegahat.org'

  action: the string to add to the HTTP header for the SOAPAction.

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.

_D_e_t_a_i_l_s:

_V_a_l_u_e:

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

_N_o_t_e:

     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.

_A_u_t_h_o_r(_s):

     Duncan Temple Lang <duncan@research.bell-labs.com>

_R_e_f_e_r_e_n_c_e_s:

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

_S_e_e _A_l_s_o:

     '.SOAP'

_E_x_a_m_p_l_e_s:

