Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Child pages (Children Display)
styleh3

Parameters

This section contains the following parameters relating to file caching, fault handling, time-out, file paths, SOAP and REST handling, and the POJO deployer.

Parameter NameDescriptionTypeDefault ValueFixed ValuesMandator/OptionalNotes
hotdeployment      
hotupdate      
enableMTOM      
enableSwA      
ConfigContextTimeoutInterval      
sendStacktraceDetailsWithFaults      
DrillDownToRootCauseForFaultReason      
userName      
password      
servicePath      
restPath      
disableREST      

 

Message Receivers

 

Message Formatters

 

Message Builders

 

Transport Ins

 

Transport Outs

 

A message receiver is a handler in Apache Axis 2.

Message receivers can be added in this section using the format shown in the example below.

Code Block
languagexml
<messageReceivers>
        <messageReceiver mep="http://www.w3.org/ns/wsdl/in-only"
                         class="org.apache.axis2.receivers.RawXMLINOnlyMessageReceiver"/>
</messageReceivers>

Message Formatters

This section is used to define message formatters to be used in scenarios where blocking transports are used. A message formatter is used to build the outgoing stream of a message. See Working with Message Builders and Formatters for more information.

Message formatters can be added using the format shown in the example below.

Code Block
languagexml
<messageFormatters>
        <messageFormatter contentType="application/x-www-form-urlencoded"
                          class="org.apache.axis2.transport.http.XFormURLEncodedFormatter"/>
</messageFormatters>

Message Builders

This section is used to define message builders to be used in scenarios where blocking transports are used. A message builder is used by transport receivers to process the raw data in the payload of a received message and convert it to the required format (e.g., SOAP). See Working with Message Builders and Formatters for more information.

Message builders can be added using the format shown in the example below.

Code Block
languagexml
<messageBuilders>
        <messageBuilder contentType="application/xml"
                        class="org.apache.axis2.builder.ApplicationXMLBuilder"/>
</messageBuilders>

Transport Ins

Transport receivers can be added in this section using the format shown in the example below.

Code Block
languagexml
  <transportReceiver name="jms" class="org.apache.axis2.transport.jms.JMSListener">
        <parameter name="myTopicConnectionFactory">
        	<parameter name="java.naming.factory.initial">org.apache.activemq.jndi.ActiveMQInitialContextFactory</parameter>
        	<parameter name="java.naming.provider.url">tcp://localhost:61616</parameter>
        	<parameter name="transport.jms.ConnectionFactoryJNDIName">TopicConnectionFactory</parameter>
		<parameter name="transport.jms.ConnectionFactoryType" locked="false">topic</parameter>
        </parameter>
  </transportReceiver>

Configurable parameters for each transport receiver are as follows.

Parameter NameDescription
java.naming.factory.initial
 
java.naming.provider.url
 
transport.jms.ConnectionFactoryJNDIName
 
transport.jms.ConnectionFactoryType
 

Transport Outs

Transport senders can be added in this section using the format shown in the example below.

Code Block
languagexml
<transportSender name="http"
                     class="org.apache.axis2.transport.http.CommonsHTTPTransportSender">
        <parameter name="PROTOCOL">HTTP/1.1</parameter>
        <parameter name="Transfer-Encoding">chunked</parameter>
        <parameter name="cacheHttpClient">true</parameter>
        <parameter name="defaultMaxConnectionsPerHost">200</parameter>
        <!-- If following is set to 'true', optional action part of the Content-Type will not be added to the SOAP 1.2 messages -->
        <!--  <parameter name="OmitSOAP12Action">true</parameter>  -->
</transportSender>

Configurable parameters for each transport sender are as follows.

Parameter NameDescriptionDefault Value
PROTOCOL
  
Transfer-Encoding
  
cacheHttpClient
  
defaultMaxConnectionsPerHost
The maximum number of connections that will be created per host server by the client. If the backend server is slow, the connections in use at a given time will take a long time to be released and added back to the connection pool. As a result, connections may not be available for some requests. In such situations, it is recommended to increase the value for this parameter.2

Global Modules

 

Clustering

 This section is used to prepare Axis2 for a clustered environment

Phases