This document shows you how to manipulate the index.html template and the tokens to customize the WSO2 Admin UI component of WSO2 Commons.
This article is the first of a set of articles that measures and compares the performance of the WSO2 ESB against other leading implementations - both Open Source and proprietary.
Editors Note: This article has been subsumed and replaced by "Writing Axis2 Services with WSO2 Developer Studio" which offers a comprehensive replacement for the old Axis2 Eclipse plugs-ins. You can download the 100% open source WSO2 Developer Studio here.
Apache Axis2 Eclipse Plugins allow Web service developers to easily and speedily expose the available plain old Java applications as Web services. This tutorial by Lahiru Sandakithconsists of two parts, with two examples that walk you through developing and deploying a sample Web service using the Top-down (Contract First) and Bottom-up (Code First) approach using Axis2 Eclipse Plugins.
Apache Axis2/C has a very extensible design and architecture. This article by Dinesh Premalal carries implementation details about libcurl based HTTP transport. Essentially, this document is targeted for an audience who has some exposure to Apache Axis2/C internals and for anyone who is seeking information about libcurl based transport implementation.
Within Apache Axis2, Jakarta Commons HTTPClient is used to send messages with HTTP and HTTPS. HTTPClient uses JSSE (Java Secure Socket Extension) to provide the https functionality. Since JSSE is part of Java 1.4 (and in later versions) there is no special configuration required for this to work.
But in some situations the default socket factory implementation is not enough. So some users might want to provide their own socket factory implementation to work with SSL. In that case Axis2 can accept a socket factory from the user so that it will be used to send that message. Let's see how this can be done.
In Apache Axis2/Java, you can deploy a POJO (Pain Old Java Object) as a Web service in several different ways, out of which the most convenient is by using a POJO Deployer.
Apache Axis2 has excellent support for sending and receiving binary payloads with SOAP using several standard mechanisms such as Base64 encoded binary, SOAP Message Transmission Optimization Mechanism (MTOM), and SOAP with Attachments (SwA). This article by Thilina Gunarathne will walk you through the SwA support in Apache Axis2.
This guide by Evanthika Amarasiri is for users who wish to report issues on the WSO2 products through JIRA. The guide will be an immense help even for beginners since it describes and gives examples for all the fields available in the JIRA issue creation page.