As we can see in the first figure, in the middle we have an object hierarchy called the AxisService hierarchy. This particular hierarchy is created using a services.xml file or the service descriptor and the hierarchy contains four types of descriptions.
When we deploy a service into Axis2, an object hierarchy will be created and added to AxisConfiguration. Therefore, unless we have services deployed in Axis2, we do not have the service objects hierarchy in the AxisConfiguration. Unlike AxisModules and other descriptions (for example, transports and message formatters), the service description hierarchy is likely to be changed at runtime, depending on the deployment options. A typical services.xml is shown next to help explain the object hierarchy in a more specific manner better:
<serviceGroup>
<parameter name="name">value</parameter>
<service name="Foo">
<parameter name="name">value</parameter>
...