NonStop SOAP 4.1 User's Manual

<module name="samplemodule" class="axis2_mod_sam">
<inflow>
<handler name="handler1" class="axis2_mod_sam">
<order phase="Transport"/>
</handler>
<handler name="handler2" class="axis2_mod_sam">
<order phase="PreDispatch"/>
</handler>
</inflow>
<outflow>
<handler name="handler3" class="axis2_mod_sam">
<order phase="MessageOut"/>
</handler>
</outflow>
<Outfaultflow>
<handler name="handler4" class="axis2_mod_sam">
<order phase="MessageOut"/>
</handler>
</Outfaultflow>
</module>
NOTE: For more information on the module.xml configuration file, see “NonStop SOAP 4
Configuration Files” (page 177).
The following table lists the configuration to achieve the handler deployment in the sample
module.xml file.
Deployment PhaseDeployment FlowHandler Name
TransportInHandler1
PreDispatchInHandler2
MessageOutOutHandler3
MessageOutOutHandler4
Creating a User-Defined Phase
NonStop SOAP 4 allows you to create user-defined phases using the axis2.xml configuration
file.
You can engage user-defined phases at different stages of the NonStop SOAP 4 message process.
The following restrictions are applicable when defining user-defined phases:
• You cannot modify the sequence of the pre-defined phases for inflow.
• You can define one or more user-defined phases to the inflow but only after the
PostDispatch phase.
• You must assign a unique name to each user-defined phase.
User-defined phases can be configured in the inflow and outflow under the phaseOrder
element of the axis2.xml configuration file.
For example, to add:
• userPhase1 to the inflow and
• userPhase2 and userPhase3 to the outflow
add the highlighted entries to the phaseOrder elements in the axis2.xml configuration file:
<phaseOrder type="inflow">
<phase name="Transport"/>
<phase name="PreDispatch"/>
<phase name="Dispatch"/>
<phase name="PostDispatch"/>
Customizing the NonStop SOAP 4 Message Process Using Handlers 131