WS Addressing enables the use of various other headers in the SOAP envelope apart from the headers, which exists when you are using WS-I Basic profile.

Some extra elements which exists when you use WS-Addressing are

MessageID, RelatesTo, To, Action, From, ReplyTo, FaultTo

All these extra headers can be used to do asynchronous Interactions.

For ex.

We will see how to implement asynchronous message exchange pattern using WS- Addressing

Use of WCF Adapter support calling of Web Services without using proxy. You have to set some extra properties when using Dynamic Send ports.

:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

MssgToSend(WCF.Action) = “SOAP Action”

MssgToSend(WCF.SecurityMode) = "None"; 

MssgToSend(WCF.TransportClientCredentialType) = "Windows";

MssgToSend(WCF.EstablishSecurityContext) = System.Boolean.Parse("true");

::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

//Asign Port Properties

DynamicSendPortSync(Microsoft.XLANGs.BaseTypes.Address)=  “End Point Uri”

DynamicSendPortSync(Microsoft.XLANGs.BaseTypes.TransportType)="WCF-BasicHttp";

::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

There is one more workaround, which you have to do, by default the FaultTo property is not promoted, so you cannot access it within the Orchestration. To use it you have to write custom pipeline component in which you can promote it.