Charitha's Web Log

By default, WSO2 Application Server (or Axis2) uses parent-first class loading mechanism. If you deploy an AAR service, which can load classes from the following locations. CARBON_HOME/lib (CARBON_HOME is the location where you installed WSO2 Application Server) CARBON_HOME/repository/deployment/server/axis2services/lib AAR service/lib (lib directory under your service archive) If your service implementation class has a package import for a class, which is available in both CARBON_HOME/repository/deployment/server/axis2services/lib and the lib directory under service archive, the class placed under CARBON_HOME/repository/deployment/server/axis2services/lib will get loaded. Which means, the parent class always get loaded first. The class loading sequence is CARBON_HOME/lib ---> CARBON_HOME/repository/deployment/server/axis2services/lib -----> AAR service/lib Sometimes, we want to load the class from service archive lib first without loading the class which is available ei...

WS-Addressing is a standard way of including message routing data within SOAP headers without relying on transport specific routing properties. If you are talking to a web service which expects WS-Addressing information in request SOAP messages, you could either follow a programmatic approach to write a client and insert WS-A headers manually or use a commercial or free web service client tool. SOAPUI is the simplest tool which can be used to insert WS-Addressing headers in to request SOAP messages. In this blog post, we will; Talk to a WS-Addressing enabled service which is hosted in WSO2 Application Server using SOAPUI Assert response SOAP message to validate WS-A headers Pre-requisites: 1. Download and install the free version of SOAPUI 3.0.1 or later 2. Download and install WSO2 Application Server 4.0 Step 1 We are going to invoke the default HelloService which is shipped with WSO2 Application Server. Go to WSO2_APPSERVER/home/bin and start the server by running wso2server.sh{ba...