Axis2/C

The Axis2/C architecture consists of flows, phases, modules and handlers.

In this article by Dushshantha Chandradasa, he discusses the use of the Secure Socket Layer (SSL) protocol for securing online transactions

In this tutorial, Supun Kamburugamuva illustrates debugging Apache Axis2/C services and clients in both Windows and Linux platforms under different deployment scenarios.

One of the main deployment scenarios of Apache Axis2/C is with Apache Web Server. Best performance and stability can be gained by deploying Axis2/C in Apache. When deployed in Apache server, Axis2/C uses the memory pools supplied by Apache and guarantees zero memory leaks. Also due to custom memory implementation Axis2/C can perform up to its maximum.

Apache Axis2/C provides facilities to the user to configure its Web Service clients to communicate with services via a proxy. This can be achieved in two different ways.

1. Configuring proxy programmatically for a particular client using service client API.

2. Enabling proxy globally for all the clients by configuring axis2.xml

In this introductory tutorial, Dimuthu Gamage explains how to use Axis2/Java tools to ease the development of Axis2/C Web Services.

This article by Lahiru Gunathilake illustrates the latest performance results of Apache Axis2/C and compares with the performance of Axis2/C with Guththila XML parser and libxml2 XML parser.

Apache Axis2/C engine uses a client repository to load its libraries, modules and services. Generally user has to specify this repository using AXIS2C_HOME environment variable. Rather than having all (libraries, modules and services) in one directory, user can specify them using axis2.xml. Dinesh Premalal, explains..