NonStop SOAP User's Manual

NonStop SOAP User-Exits
NonStop SOAP User’s Manual—520501-012
C-8
Nonstop Soap Server User-Exit Processing Flow
is expected by the NonStop SOAP server, as defined by the response DDL description
for the service.
Pre_Marshal_Header() User-Exit
Input: SOAP Response XML document
Output: SOAP Response XML document
The following actions are associated with the Pre_Marshal_Header user-exit:
°
Invoked after the default Marshal() method executes (the name of this user-
exit is misleading)
°
Used to modify the SOAP Response header; header elements such as “routing
path,” “version,” “encoding type,” and so on, may be modified
Post_Process() User-Exit
Input: SOAP Response XML document
Output: SOAP Response XML document
The Post_Process user-exit allows for any final modification of the SOAP Response
XML document before it is sent to the service consumer.
Therefore, to summarize the actions that may be performed by each user-exit:
•
To modify the SOAP Request XML document, the Pre_Process() user-exit is
used.
•
To modify the SOAP Request structure, the Pre_Service() user-exit is used.
•
To bypass the default service invocation, the skipService() method is called
from the Pre_Process() or Pre_Service() user-exits. If skipService() is
in effect:
°
The Pre_Service() user-exit creates the expected Service Request buffer,
explicitly calls the service provider, and receives the response.
°
The Service Response buffer is transformed into the SOAP Response
structure by the Pre_Service() or Pre_Marshal() user-exits.
•
To modify the SOAP Response structure, the Pre_Marshal() user-exit is used.
•
To modify the SOAP Response header, the Pre_Marshal_Header() user-exit
is used.
•
To modify the SOAP response XML document, the Post_Process() user-exit is
used.