+

Search Tips   |   Advanced Search

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.

Perform 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 creating a Web service, we 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 V7.0 clients always include WS-Addressing information if the service WSDL file includes the UsingAddressing element, regardless of the value of the required attribute.

If we are creating a client application to use a service from another provider, we 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, we 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.


Table 1. The behavior of the WS-Addressing support in WAS ND

  The WSDL for the service specifies UsingAddressing required = "false" The WSDL for the service specifies UsingAddressing required = "true" 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 WAS ND. The WS-Addressing information is processed by WAS ND. The WS-Addressing information is processed by WAS ND.
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 WAS ND. The message automatically contains the mandatory WS-Addressing information, as defined in the WS-Addressing specification. The information is processed by WAS ND. WS-Addressing information is not added. The message is accepted.

 

 

Results

WS-Addressing properties are now included in the SOAP message header, and are processed by the server on receipt of the message.

 

Related tasks


Enable Web Services Addressing support for JAX-WS applications
Develop applications that use Web Services Addressing

 

Related


IBM proprietary Web Services Addressing SPIs