Knowledge Base

Deepal Jayasinghe explains..

Apache Axis2/Java supports interfacing with proxies via HTTP Client 3.0.1. This configuration is achieved programmatically, or, by editing the axis2.xml file. In addition to this, you can also employ Java networking properties to configure proxy interfacing. Saminda Abeyruwan explains..

Web service implementations might need to be provided with additional parameters when they initialize and start serving requests. This article explains how and where these parameters can be kept so that the Web service will be able to access them at runtime. Eran Chinthaka explains..

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..

Apache Axis2 provides session management capabilities for both client and server sides. Axis2 supports four levels of session scopes. Charitha Kankanamge explains.

1. Request
2. soapsession
3. application
4. transportsession

You can deploy your Web service using any of the above session scopes. In this story, we are discussing Transportsession scope, in which we highlight how a service is deployed in transport session scope and how to test transport session management, in a simple RESTful manner.

This document by Chintana Wilamuna provides, a detailed and visual guide to installing WSO2 WSF/PHP on the Uniform Server. The Uniform Server is a WAMP, that runs on MS Windows without having to install any additional software on your computer.

When we invoke a service in a session-aware manner, i.e. deploy a service in a SOAP session we need to send the ServiceGroupId. This is not a problem if we use the same ServiceClient instance, however, if we are going to use two or more different instances of ServiceClient then it is somewhat difficult to do so. When we have single client we can get the SOAP session working using following two steps:

When we invoke a service in a session-aware manner, deployed using SOAP, we need to retrieve the ServiceGroupId. This is not a problem if we use the same ServiceClient instance, however, when we use two or more different instances of a ServiceClient, then it is somewhat difficult to do so. In this story by Deepal Jayasinghe, he explains how to this can be done.