Release 10.1A: OpenEdge Development:
Web Services

> ## Defining SOAP header callback procedures

> In general, you can define the internal procedure for a callback in any procedure context that is guaranteed to be active at the time you execute the `SET-CALLBACK-PROCEDURE( )`method, and that remains active until after the callback procedure is executed by OpenEdge. The time of this execution depends on the type of request:

> - Synchronous Web service requests — For either a SOAP request header callback or a SOAP response header callback, the procedure context must remain active until the operation invocation has completed execution.

> - Asynchronous Web service requests — For a SOAP request header callback, the procedure context must remain active until the operation invocation has completed execution. For a SOAP response header callback, the procedure context must remain active until activation of the `PROCEDURE-COMPLETE` event for the request and any results have been returned to the `PROCEDURE-COMPLETE` event procedure.

> For each type of callback procedure that you define, you must provide a specific procedure signature. For more information on this signature, see Chapter 11, " Handling SOAP Message Headers in the Progress 4GL."

Copyright © 2005 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095