Development of Web Service applications based on was CE and AXIS2

Introduction

In recent years, with the rapid development of Web service technology, applications based on Web service development have been used more and more widely. The good encapsulation of WEB service and cross-platform capabilities provide a viable solution for application integration, business-to-business integration, and more. This article describes how to use was CE (WebSphere application Server Community Edition) and Apache Axis2 to develop, deploy, and test a simple Web service application-online florist.

1. Introduction of application and operation environment

1.1 was CE introduction

WebSphere Application Server Community Edition is a lightweight Java application server built by IBM based on the Open source project Apache Geronimo Technology, which is WebSphere application New member of the server product family. It conforms to the Java 2 Enterprise Edition (EE) V1.4 specification and, like all Java EE application servers, provides a platform for running multi-tiered enterprise-class applications.

This article describes a Web service application example-the development, deployment, and testing process of an online florist. Was CE provides web containers for the SOAP engine Axis2 used for online florist services and provides a built-in derby database for data access. In the example in this article, the was CE v1.0.1.2 version was used, but also provided for the Apache GeronimoV1.1 version of the Derby data source and AXIS2 deployment plan in the sample code download. Readers can choose a different deployment plan depending on which server they use.

1.2 Axis2 Introduction

The Apache Axis2 is a follow-on version of Axis and is a new generation of soap engines.

The main features of AXIS2 are:

Using the new core XML processing model named AXIOM (AXIs object model), using the flexibility provided by the new XML parser to construct the object model on demand

Support for different message exchange modes. Currently, AXIS2 supports three modes: In-only, robust-in and In-out. The IN-ONLY message Exchange Mode has only SOAP requests and does not need to be answered;

Robust-in the message Exchange Mode sends a SOAP request and returns an answer only if there is an error; the In-out message exchange Mode always has a SOAP request and a reply.

Provides blocking and Non-blocking client APIs

Support for built-in Web service Addressing (ws-addressing)

Flexible data binding, you can choose to use AXIOM directly, use a simple data binding method similar to the original Axis, or use a dedicated data binding framework such as XMLBeans, JiBX, or JAXB 2.0

New deployment model, support for hot deployment

Support for HTTP,SMTP,JMS,TCP Transport protocol

Support Rest (representational state Transfer)

The specifications supported by AXIS2 include:

SOAP 1.1 and 1.2

Message transmission optimization Mechanism (MTOM), XML optimized packaging (XOP) and SOAP with Attachments

WSDL 1.1, including both SOAP and HTTP bindings

Ws-addressing (submission and final)

Ws-policy

SAAJ 1.1

For more detailed introduction of AXIS2, you can visit the AXIS2 website http://ws.apache.org/axis2/.