...
- 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.
- The use of WS-Addressing is indicated by one of the following:
- A <UsingAddressing xmlns="http://www.w3.org/2005/02/addressing/wsdl"> element is attached to the <wsdl:port>, <wsdl:service> or <wsdl:binding> element.
- 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/policy
, http://www.w3.org/2005/02/addressing/wsdl
, http://www.w3.org/2006/05/addressing/wsdl
.
- 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/addressing. 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. |
...