Version 0.94
Feedback: axis-dev@ws.apache.orgAny architecture is a result of what that architecture should yield. The success of an architecture should be evaluated based on the requirements expected to be met by that architecture. Let us start our journey into Axis2 by looking at the requirements.
In the SOAP terminology, a participant who is taking part in a Web Service interaction is known as a SOAP Node. Delivery of a single SOAP Message is defined based on two participants, SOAP Sender and SOAP Receiver. Each SOAP Message is sent by SOAP Sender and received by SOAP Receiver. A single SOAP delivery is the most basic unit that builds the Web Service interaction.
Each SOAP Node may be written in specific programming language, may it be Java, C++, .NET or Perl, the Web Services allow them to inter operate. This is possible because on the wire each Web Service interaction is done via SOAP, which is common to every SOAP Node.
Web Service middleware handles the complexity in SOAP messaging and lets the users work with the programming language they are accustomed to. Axis2 allows java users to invoke Web Services using java representations, and handles the SOAP messaging behind the curtain.
Axis2 handles SOAP processing along with numerous other tasks. This makes the life of the Web Service developer a whole lot easier. Following are the identified requirements: