Use the IBM proprietary Web Services Addressing SPIs: Performing more advanced Web Services Addressing tasks

WAS v9 provides proprietary system programming interfaces for more advanced Web Services Addressing (WS-Addressing) tasks, which involve the WS-Addressing message-addressing properties passed in the SOAP header of a web service message. We can also use the SPIs to choose a WS-Addressing specification level other than the default used by the product.

We cannot use the standard JAX-WS API classes with these proprietary SPIs. However, we can convert endpoint references created using the standard JAX-WS API classes to instances of the com.ibm.websphere.wsaddressing.EndpointReference class, using the com.ibm.websphere.wsaddressing.jaxws21.EndpointReferenceConverter class. We can then use these converted endpoint references with the SPIs.

The steps described in this task apply to servers and clients that run on WebSphere Application Server.

Complete this task to specify or acquire WS-Addressing message-addressing properties, or if we have an application that needs to interoperate with a client or endpoint that is not using the default WS-Addressing specification supported by this product.

Tasks

• To manipulate message-addressing properties, follow the instructions in Specify and acquiring message-addressing properties using the IBM proprietary Web Services Addressing SPIs

• To interoperate with the pre-W3C specification of WS-Addressing, with the namespace http://schemas.xmlsoap.org/ws/2004/08/addressing, refer to Interoperating with Web Services Addressing endpoints that do not support the default specification supported by WAS.

Subtopics

• Specify and acquiring message-addressing properties using the IBM proprietary Web Services Addressing SPIs
  Using the proprietary Web Services Addressing (WS-Addressing) system programming interfaces (SPIs), we can add WS-Addressing message addressing properties (MAPs) to the SOAP headers of an outbound client message, through properties on the JAX-WS BindingProvider request context, or the JAX-RPC Stub or Call object. When the target endpoint receives the message, the SPI enables the endpoint to acquire the MAPs through properties on the message context.
• Interoperating with Web Services Addressing endpoints that do not support the default specification supported by WAS
  A target web service endpoint might not support the same Web Services Addressing (WS-Addressing) namespace as this product. In most cases, we do not have to undertake any extra actions to interoperate with such endpoints, however some scenarios require additional steps in the implementation of our web service.

Related:

IBM proprietary Web Services Addressing SPIs