An operation type defines the expected use of the WSDL input, output and fault elements in the WSDL definition.
The operation type does impose some requirements on the flow (for example, whether the broker is initiating the interaction or listening). It is your responsibility to construct an appropriate flow for the operation type.
The presence and ordering of input and output messages implicitly defines the operation type in WSDL 1.1. For example a WSDL operation defining a single wsdl:input followed by a single wsdl:output implies that the operation type is request-response. Zero or more (*) wsdl:fault definitions may also appear and the Web service would return either the expected output message or one of the defined faults messages.
Operation Type | Description | Analogous to... | Order of Messages |
---|---|---|---|
request-response | client calls Web service – response expected | method call | Input output fault* |
solicit-response | Web service solicits client – response expected | callback | output input fault* |
one-way | client calls Web service – no response expected | procedure – no return | input |
notification | Web service calls client – no response expected | signal – no response | output |
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ac34650_ |