The SOAP 1.1 operation element provides binding information from the abstract operation to the concrete SOAP operation.
Table 3 SOAP 1.1 operation Element Attributes
Property |
Description |
Required or Optional |
Example |
---|---|---|---|
soapAction |
Indicates the soapAction that should be put into the HTTP header |
Optional |
urn:someSoapAction |
style |
Indicates the default style of this particular SOAP operation |
Optional |
rpc |
The following example illustrates the use of the SOAP operation element.
<definitions .... > <binding .... > <operation .... > <soap:operation soapAction="uri"? style="rpc|document"?>? </operation> </binding> </definitions> |
The style attribute indicates whether the operation is RPC-oriented, with messages containing parameters and return values, or document-oriented, with messages containing documents. This information is used to select an appropriate programming model. The value of this attribute also affects the way in which the body of the SOAP message is constructed. If the attribute is not specified, it defaults to the value specified in the soap:binding element. If the soap:binding element does not specify a style, it is assumed to be "document".
The soapAction attribute specifies the value of the SOAPAction header for this operation. Use this URI value directly as the value for the SOAPAction header. do not attempt to make a relative URI value absolute when making the request. For the HTTP protocol binding of SOAP, this value is required and has no default value. For other SOAP protocol bindings, this value should not be specified, and the soap:operation element can be omitted.