Versions Compared

Old Version 8

changes.mady.by.user Andrea Smyth

Saved on

compared with

New Version Current

changes.mady.by.user Glen Mazza

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

...

  1. The addressing interceptors (org.apache.cxf.ws.addressing.MAPAggregator and org.apache.cxf.ws.addressing.soap.MAPCodec) need to be on the inbound and outbound interceptor chains.
  2. The use of WS-Addressing is indicated by one of the following:
    1. A <UsingAddressing xmlns="http://www.w3.org/2005/02/addressing/wsdl"> element is attached to the <wsdl:port>, <wsdl:service> or <wsdl:binding> element.
    2. The (chosen alternative for the) effective policy of the message contains a <Addressing xmlns="http://www.w3.org/2007/02/addressing/metadata"> assertion or a <UsingAddressing> assertion from either one of the following three namespaces: http://schemas.xmlsoap.org/ws/2004/08/addressing/policyImage Removed, http://www.w3.org/2005/02/addressing/wsdlImage Removed, http://www.w3.org/2006/05/addressing/wsdlImage Removed.
    3. Property org.apache.cxf.ws.addressing.using in the message context is set to Boolean.TRUE.

...

The addressing feature element is defined in namespace http://cxf.apache.org/ws/addressingImage Removed. It supports two attributes:

Name

Value

allowDuplicates

A boolean that determines if duplicate MessageIDs are tolerated (default: true)

usingAddressingAdvisory

A boolean that indicates if the presence of the <UsingAddressing> element in the wsdl is purely advisory, i.e. its absence doesn't prevent
the encoding of WS-A headers. This is especially useful to enable WS-Addressing in the java-first case, where you have no wsdl and hence none of the conditons conditions in 2.1 and 2.2 will be met.

...

org.apache.cxf.ws.addressing.MAPAggregator and org.apache.cxf.ws.addressing.soap.MAPCodec must be added to the interceptor chain for inbound and outbound messages and faults.
On a global level, i.e. applicable to all client and server endpoints, this can be done as in the example below (see also Bus Configuration). Note that, as allowDuplicates and usingAddressingAdvisory are actually properties of the MAPAggregator interceptor, they can also be set using Spring syntax.

...