Axis2 > Java

This article by Eran Chinthaka describes the requirement of understanding the mustUnderstand SOAP header property in designing and implementing Web services.

In this tutorial by Deepal Jayasinghe, he provides a step-by-step guide to creating services that handle binary data together with instructions on creating clients that consume such services.

It is often a requirement to debug Web services as they are deployed within Axis2. Once we have Axis2 deployed within a servlet container, we are able to use the debugging capabilities of those virtual machines in order to debug any Web applications deployed within them. This article by Eran Chinthaka describes debugging Web services deployed in Axis2 running on Apache Tomcat.

One of the new features introduced in Apache Axis 1.4 is the ability to apply policies at the binding hierarchy. Prior to Axis2 1.4, we were only able to apply policies at server level, operation level and message level and those policies were applied to all the SOAP bindings. But with Axis2 1.4, we can apply policies at diffrent policy subjects in binding hierarchy using the new policy configuration.

In this article by Deepal Jayasinghe, he introduces the use of custom deployers to gain most out of your Axis2 deployment.

Often times the requirement comes up to send a SOAP envelope to a different location than what's specified inside WS-Addressing 'To' address. This knowledge base by Eran Chinthaka outlines how.

Some times we might want to perform various actions, depending on the current service and operation. This knowledge base outlines how one can find the service and the operation associated with the message being processed.

In Axis2, there are four types of sessions that we talk about. Each session has a lifetime and characteristics specific to the session type. The available sessions in Axis2 can be listed as follows:

1. Request scope

2. SOAP session scope

3. Transport session scope

4. Application session scope

   0

   No votes yet