This section describes how to manage Web service operations (or methods). These procedures require that you:
Expand the Web service collection.
Expand the Web service.
Expand the operations folder.
If you deploy a Web service that contains overloaded methods, the WST development tool displays only the first method of the overloaded method. Allowing or disallowing access to the method, affects all overloaded methods.
For example, if the Web service contains an overloaded method that contains the methods echo(String, String) and echo (String), the GUI displays only echo (String, String) twice, but the allowed/disallowed operation affects both echo(String, String) and echo(String).
Invoking an operation
This procedure invokes an operation of the Web service to which it belongs.
Right-click the operation and then select Invoke.
Allowing an operation
Allowing a Web service operation makes it available to clients. If a Web service operation is already allowed, this option is dimmed.
Right-click the operation and then select Allow.
Disallowing an operation
Prevent access to a Web service operation by following this procedure. If a Web service operation is already disallowed, this option is dimmed.
Right-click the operation and then select Disallow.
Table 4-5 describes the Web service operation properties.
Property type |
Property |
Description |
|---|---|---|
General |
Name |
The name of the operation. |
Description |
A description of the Web service operation. |
|
Style |
The SOAP binding style:
|
|
Return Type |
Specifies the return type of the operation. |
|
Is return value in response message |
True or false. |
|
SOAP Action |
The URI for the SOAPAction HTTP header for the HTTP binding of SOAP. The SOAPAction HTTP request header field can be used to indicate the intent of the SOAP HTTP request. The URI identifies the intent. |
|
Message Operation Style |
Document, RPC, or wrapped. |
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
