Try OpenEdge Now
skip to main content
Web Services
Creating ABL Clients to Consume OpenEdge SOAP Web Services : Invoking OpenEdge SOAP Web Service Operations from ABL : Managing asynchronous requests : Results handling
 
Results handling
A few differences exist in the results returned for an asynchronous Web service request compared to an asynchronous AppServer request, as shown in the following table.

Results for asynchronous Web service requests

ABL result elements
Web service request result
ERROR-OBJECT
Returns an object reference to an instance of a class that implements Progress.Lang.SoapFaultError.
ERROR-STATUS system handle
If the ERROR attribute of the asynchronous request object handle is set to TRUE because of a SOAP fault, the ERROR-STATUS:ERROR-OBJECT-DETAIL attribute references a SOAP-fault object handle with information on the SOAP fault.
RETURN-VALUE function
The value for ABL RETURN-VALUE function is never altered directly by the response from a Web service asynchronous request.
STOP condition
The client can raise the STOP condition by executing the CANCEL-REQUESTS( ) method on the Web service server object handle. All outstanding Web service requests are handled in a similar manner to those on an AppServer, except that for any currently executing Web service requests, the result is undefined. OpenEdge disconnects from all ports to currently executing Web service requests, and the exact response depends on how the Web service responds to the lost connection.