This documentation is for WSO2 Carbon 4.2.0. View documentation for the latest release.
Page Comparison - Configuring axis2.xml (v.1 vs v.2) - Carbon 4.2.0 - WSO2 Documentation

Versions Compared

Key

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

...

Click on the table and use the left and right arrow keys to scroll horizontally. For sample values, see the Example below the table.

XML Elements 
Anchor
elements
elements

XML elementAttributesDescriptionData typeDefault valueMandatory/Optional
<axisconfig> name The root element. The name is defined as: name="AxisJava2.0"  Mandatory
<module>refA globally engaged module. The ref attribute specifies the module name.  Mandatory
<parameter>

name

locked

A parameter is a name-value pair. All top-level parameters (those that are direct sub-elements of the root element) will be transformed into properties in AxisConfiguration and can be accessed in the running system. The name attribute (required) specifies the parameter name. If you set the locked attribute to true (default is false), this parameter's value cannot be overridden by services and other configurations.  Mandatory
<listener>classA registered listener that will be automatically informed whenever a change occurs in AxisConfiguration, such as when a service or module is deployed or removed. The class attribute specifies this listener's implementation class, which must implement the AxisObserver interface.

Registering listeners is useful for additional features such as RSS feed generation, which will provide service information to subscribers.
  Optional
<messageReceivers> 

The container element for messages receiver definitions. 

  Mandatory
<messageReceiver>

class

mep

A message receiver definition. The class attribute (required) specifies the message receiver implementation class. The mep attribute (required) specifies the message exchange pattern supported by this message receiver. Each message receiver definition supports only one MEP.  Mandatory
<messageFormatters> The container element for message formatter definitions, which are used to serialize outgoing messages to different formats (such as JSON). The format for a message can be specified by setting the "messageType" property in the MessageContext. It can also be specified as a parameter in service.xml (for service-based configuration) in addition to axis2.xml (for global configuration).  Optional
<messageFormatter>

contentType

class

A message formatter definition. The contentType attribute specifies which message types are handled by this formatter, and the class attribute specifies the formatter implementation class.  Optional
<messageBuilders> The container element for the message builder definitions, which are used to process the raw payload of incoming messages and convert them to SOAP.  Optional
<messageBuilder>

contentType

class

A message builder definition. The contentType attribute specifies which message types are handled by this builder, and the class attribute specifies the builder implementation class.  Optional
<transportReceiver>

name

class

A transport receiver definition, one for each transport type. The name attribute specifies the short name to use when referring to this transport in your configurations (http, tcp, etc.), and the class attribute specifies the receiver implementation class that provides the logic for receiving messages via this transport. You can specify <parameter> elements to pass any necessary information to the transport.  Mandatory
<transportSender> Just like <transportRecevier>, except <transportSender> allows you to define transport senders, which are used to send messages via the transport.  Mandatory
<phaseOrder>type

Specifies the order of phases in the execution chain of a specific type of flow (specified by the type attribute), which can be one of the following:

  • InFlow
  • OutFlow
  • InFaultFlow
  • OutFaultFlow

You add phases using the <phase> sub-element. In the In phase orders, all phases before the Dispatch phase are global phases and after Dispatch are operation phases. In the Out phase orders, phases before the MessageOut phase are global phases and after MessageOut are operation phases.

  Mandatory
<phase>nameThe phase definition. The name attribute specifies the phase name. You can add the <handler> sub-element to execute a specific handler during this phase.  Mandatory
<handler>

name

class

The handler (message processing functionality) to execute during this phase. Handlers are combined into chains and phases to provide customizable functionality such as security, reliability, etc. Handlers must be multi-thread safe and should keep all their state in Context objects (see the org.apache.axis2.context package).  Optional
<order>phase   Optional
<clustering>

class

enable

Used to enable clustering. The class attribute specifies the clustering agent class. The enable attribute is false by default; set it to true to enable clustering.  Optional
<property>    Optional
 name    
 value    
_ _<members> The list of static or well-known members. These entries will only be valid if the "membershipScheme" above is set to "wka" N/AOptional
_ _ _<member>   N/AOptional
_ _ _ _<hostName>   N/AOptional
_ _ _ _<port>   N/AOptional
_ _<groupManagement> Enable the groupManagement entry if you need to run this node as a cluster manager. Multiple application domains with different GroupManagementAgent implementations can be defined in this section.  Optional
 enable  FALSE 
_ _ _<applicationDomain>   N/AOptional
 name    
 port    
 subDomain    
 agent    
 description    

Example
Anchor
example
example

The following example shows excerpts from an axis2.xml file.

...