NonStop SOAP 4.1 User's Manual

<order/>
</handler>
</INfaultflow>
<Outfaultflow>
<handler>
<order/>
</handler>
</Outfaultflow>
</module>
where,
<module>
represents the entire module to be configured.
<inflow>
represents a collection of one or more <handler> elements that must be invoked while
processing the input flow for a particular message.
<handler>
represents the unit or class that must be invoked by the NonStop SOAP 4 server. Multiple
handlers can be used.
<order>
represents the order and phase in which its parent handler must be invoked.
The module.xml file is used to perform the following tasks:
• “Specifying the Module Name and Module Class File Name” (page 191)
• “Defining a New Handler and Specifying its Invocation Order” (page 191)
Specifying the Module Name and Module Class File Name
The module element must be updated with the module name and the class name. The sample
syntax to specify the module name and class file name in the module.xml file is:
<module name="module-name" class="module-class">
where,
name
is the name of the module to be configured. This is a mandatory attribute.
class
is the module class name. If the module DLL name is libaxis2_mod_log.so, the class value
will be axis2_mod_log. This is a mandatory attribute.
Defining a New Handler and Specifying its Invocation Order
A module is a collection of handlers. To add a handler, specify the handler name and the handler
class name in the <handler> element of the module.xml file as:
<handler name=”handler-name” class=”handler-class”>
where,
name
is the name of the handler. This is a mandatory attribute.
class
specifies the DLL that implements the handler. If the name of the DLL is
libaxis2_loghandler.so, the class value will be loghandler.
The module.xml file provides the flexibility to decide when a particular handler must be invoked
within a given phase. The <order> element has attributes that can help invoke handlers depending
The module.xml File 191