Knowledge Base

One of the main deployment scenarios of Apache Axis2/C is with Apache Web Server. Best performance and stability can be gained by deploying Axis2/C in Apache. When deployed in Apache server, Axis2/C uses the memory pools supplied by Apache and guarantees zero memory leaks. Also due to custom memory implementation Axis2/C can perform up to its maximum.

Apache Axis2/C provides facilities to the user to configure its Web Service clients to communicate with services via a proxy. This can be achieved in two different ways.

1. Configuring proxy programmatically for a particular client using service client API.

2. Enabling proxy globally for all the clients by configuring axis2.xml

In this document by Asankha Perera, he describes the basic steps to be followed when deploying the WSO2 Enterprise Service Bus (ESB) into a WebLogic 10 application server. The WSO2 ESB is an open source Enterprise Service Bus from WSO2, released under the Apache License v2.0 from WSO2.

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.

Problem: My POJO method has meaningful names for parameters. But when I deploy this as a web service in Axis2/WSAS, WSDL shows parameter names as param0,param1... etc. This is very confusing for clients of the service. How can I avoid this?

The WS-MetaDataExchange specification defines protocols that support the dynamic exchange of metadata that is relevant to the service interaction (such as XML Schema WS-policy and WSDL descriptions) between Web services endpoints. WS-MetadataExchange specification  provides more information you need to know about it.

This KB gives you a few guidelines to for selecting whttp:locations for your operations. Please refer [1] to find out what a whttp:location is.

The location property which is defined under the WSDL 2.0 HTTP Binding Namespace (http://www.w3.org/ns/wsdl/http) specifies a pattern for serializing input message instance data into the request URI.