Adding an operation

About this task

An operation names the operation and lists the expected inputs and outputs. The operation element may also contain a fault sub-element that describes any error data that the operation may return.

Using an operation, you can declare four transmission primitives that an endpoint can support:

One-way: the endpoint receives a message.
Request-response: the endpoint receives a message, and sends a correlated message.
Solicit-response: the endpoint sends a message, and receives a correlated message.
Notification: the endpoint sends a message.

You can add an operation to a port type or a port binding.

Note: Changes of service elements are not automatically propagated to bindings. You need to regenerate the binding content and select the Overwrite existing binding information check box in the binding wizard to reflect changes in the WSDL. For more information, see Setting a binding.

To add an operation to a port type, complete the following steps:

Procedure

In the design workspace, right-click your port type. Click Add Operation.
The Properties view of the new operation opens. In the General tab, type the name of the operation in the Name field.
Type any information about the operation you wish the user to read in the Documentation tab.
To manage extensions, click the Extensions tab. You can either add, sort, or remove extensions.
Right click on the operation to add input, output or fault objects. Depending on an operation's inputs and outputs it can be classified as follows:
- One way operation: input
- Request response operation: input, output
- Solicit response operation: output, input
- Notification operation: output

Results

Note that if the operation is not defined in any binding, an error icon will automatically show on operation node in the Repository tree view.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!

Leave your feedback here