Deploying an axis2 service in application scope
If you deploy a service without specifying a scope, it will be considered as sessionless and will be deployed in request session scope. In other words, request scope is the default session scope of an axis2 web service. When a service is deployed in request session scope, an instance of the service implementation class is created for every invocation. Suppose you want to get rid of that and maintain a single instance of service class throughout the server life time. Then you should deploy the service in application session scope. Lets see how it can be achieved and tested the service invocation using WSO2 WSAS. First, create a simple java bean as follows. public class Employee { private int Age; private String name; private String emp_id; public int getAge() { return Age; } public void setAge(int age) { Age = age; } public String getName() { return name; } public void setName(String name) { this.name = name; } public String getEmp_id() {