NonStop SOAP 4.1 User's Manual

The handlers attached to the PostDispatch phase can access the service name and operation

name of the target service for which the message is intended after the PostDispatch phase. The

handlers in this phase perform the following tasks:

• Get/Set the service name

• Get/Set the operation name

• Update the message context structure

PostDispatch

This phase verifies if the dispatchers have been able to find a service and an operation for the

message. If not, the processing of the message halts and an error is reported.

NOTE: NonStop SOAP 4 does not allow you to change the sequence of inflow.

The handlers in this phase verify if the dispatchers have been able to find a service and an operation

for the message. If a service is not found, the handlers report an error. The handlers in this phase

perform the following tasks:

• Get/Set the service name

• Get/Set the operation name

• Skip the service invocation

• Update the message context structure

User-defined phases in inflow

You can define phases in the inflow only after the PostDispatch phase. This is because the

default phase order of pre-defined phases cannot be changed and the first phase in inflow must

be the transport phase.

The handlers in the user-defined phase perform the following tasks:

• Get/Set the service name

• Get/Set the operation name

• Skip the service invocation

• Update the message context structure

For example:

</phaseOrder>

where,

myPhase

is a user-defined phase.

Pre-defined phases in outflow

The outflow comprises a set of pre-defined phases in the following sequence:

1. “MessageOut” (page 130)

2. “Transport” (page 130)

Customizing the NonStop SOAP 4 Message Process Using Handlers 129