Network Deployment (Distributed operating systems), v8.0 > Develop and deploying applications > Develop web services - Addressing (WS-Addressing)


Enable Web Services Addressing support for JAX-RPC applications

The Web Services Addressing (WS-Addressing) support provides mechanisms to address web services and provide addressing information in messages.

To enable the WS-Addressing support for JAX-RPC applications, either configure the WSDL file for a service that runs on WAS, or use the WS-Addressing API or system programming interface (SPI) to add WS-Addressing properties in a WAS client.

Complete this task to enable the WS-Addressing support, either as a service provider or as a client of a service provided by another party. This task also describes how to disable the WS-Addressing support, which can improve performance for those applications that do not use WS-Addressing or any protocol that depends on the WS-Addressing support.

If you are creating a web service, you can enable the WS-Addressing support during development of the service, by including the UsingAddressing extensibility element in the WSDL binding element for the service. This element contains a required attribute that has a value of either false, which specifies that WS-Addressing information is accepted but not required in incoming messages, or true, which specifies that WS-Addressing information is required in incoming messages. The default value is false. Messages from WAS clients always include WS-Addressing information if your service WSDL file includes the UsingAddressing element, regardless of the value of the required attribute.

If you are creating a client application to use a service from another provider, you might not have access to the WSDL file for the service, or the service might use a version of WSDL that does not support the UsingAddressing element (if the service is not running on a current version of this product). However, you can still enable WS-Addressing support, during run time, by setting WS-Addressing properties on the JAX-RPC stub or call object that you use to communicate with the service.

The following table summarizes the behavior of the WS-Addressing support in each of the scenarios mentioned previously.

The behavior of the WS-Addressing support in the product. The table details the resulting behavior of different UsingAddressing settings when an application server client sends a message.

  The WSDL for the service specifies UsingAddressing required = "false" The WSDL for the service specifies The WSDL for the service does not specify UsingAddressing
A client sends a message that contains WS-Addressing information The WS-Addressing information is processed by the product. The WS-Addressing information is processed by the product. The WS-Addressing information is processed by the product.
A non-WAS client sends a message that does not contain WS-Addressing information The message is accepted. The service returns a fault. The message is accepted.
A WAS client sends a message, without specifying addressing properties The message automatically contains the mandatory WS-Addressing information, as defined in the WS-Addressing specification. The information is processed by the product. The message automatically contains the mandatory WS-Addressing information, as defined in the WS-Addressing specification. The information is processed by the product. WS-Addressing information is not added. The message is accepted.


Procedure


Results

WS-Addressing properties are now included in the SOAP message header, and are processed by the server on receipt of the message.
IBM proprietary Web Services Addressing SPIs
Enable Web Services Addressing support for JAX-WS applications
Develop applications that use Web Services Addressing

+

Search Tips   |   Advanced Search