uCosminexus Application Server, Web Service Development Guide

[Contents][Glossary][Index][Back][Next]

10.13.1 Selecting the SOAP version (when developing Web Services)

This subsection describes how to select the version for developing Web Services starting from a WSDL, SEI, and provider.

Organization of this subsection
(1) Starting from a WSDL
(2) Starting from SEI
(3) Starting from a provider

(1) Starting from a WSDL

To send or receive messages of the SOAP 1.1 specifications or the SOAP 1.2 specifications is determined from the binding coded in the WSDL.

The skeletons of the Web Service Implementation Class generated using the cjwsimport command exists for each binding, so the skeletons are dedicated to either SOAP 1.1 specifications or the SOAP 1.2 specifications. You cannot dynamically change the skeletons during the execution.

On the other hand, as you can code multiple bindings in a WSDL, you can mix the ports of the SOAP 1.1 and SOAP 1.2 specifications in a single WSDL.

The following is an example of mixing the ports of the SOAP 1.1 and SOAP 1.2 specifications:

Figure 10-8 Example of mixing ports

[Figure]

With this example, bind a single port type separately to use with SOAP 1.1 and SOAP 1.2. This enables a single port type to receive messages of the format conforming to the SOAP 1.1 and SOAP 1.2 specifications.

(2) Starting from SEI

Use annotations to specify whether to bind to the SOAP 1.1 specifications or the SOAP 1.2 specifications. Specify an annotation for each Web Service Implementation Class. You cannot dynamically change the annotations during the execution.

You can omit annotations. If omitted, the SOAP 1.1 specifications will be applicable.

(3) Starting from a provider

Use annotations to specify whether to bind with the SOAP 1.1 specifications or the SOAP 1.2 specifications. Specify an annotation for each Provider Implementation Class. You cannot dynamically change the annotations during the execution.