You have already reviewed a number of features and ways to use Axis2 in previous articles. The main focus of this article is to discuss some of the terms you encounter when you read Axis2 articles and documents. Axis2 it keeps its data and logic separately. That provides much flexibility and extensibility into Axis2. When you look at Axis2 data, it consists of two main parts, static data and dynamic data. In this article, I will discuss Axis2's static data hierarchy. At the end of the article, you will be able to understand Axis2 static data hierarchy and different type usage of them.
Axis2 Static Hierarchy
As the name implies, static data are the data that is not going to change over the time. However, it should be noted here that some of the configuration data I will discuss here may be changed over time. In other words, you can change them at runtime. Most of the data come from various configurations that you find in Axis2. In Axis2, you easily can find three types of configuration that make the static data hierarchy:
- Global level configuration file: axis2.xml
- Service level configuration file: services.xml
- Module or service extension configuration file: module.xml
The global configuration file is called "axis2.xml" and contains all the bare minimum configuration data needed to start an Axis2 server. Meanwhile, you can edit your axis2.xml file to suit your requirements and start Axis2 using the edited file. A typical axis2.xml file has the following set of configuration options.
- Deployment configuration data
- Transport senders
- Transport receivers
- Execution chains
- Phases
- Parameters
- Message formatters and Message builders
Read the Rest of this Article at Developer.com