Method 2: Client Request Sending WS-Addressing Information
The run-time processing steps are as follows:
1. Client sends the request with WSA Header information to Mediator.
In this example, the request has the WSA header information. For example:
2. Since the client request contains the WSA header information, Mediator acts as a transparent proxy server.
Mediator receives the request and routes it to the native service endpoint without interfering, it does not process the WSA header information. For example:
3. Native service receives the request from Mediator, processes it, and sends a WSA response to Mediator.
For example:
4. Mediator sends the response to the client with WSA header information.
For example:
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing">
<wsa:MessageID>
urn:uuid:3D1339DB6EBF8671642930492696797-1700958707
</wsa:MessageID>
<wsa:Action>
http://Username.Domain/service/AddInts_WSD_PortType/AddIntsR
esponse
</wsa:Action>
<wsa:RelatesTo>Test Message</wsa:RelatesTo>
</soapenv:Header>
<soapenv:Body>
<ser-root:AddIntsResponse xmlns:ser-root="http://Username.Domain/
service" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<C>50</C>
</ser-root:AddIntsResponse>
</soapenv:Body>
</soapenv:Envelope>
Note: The pg.proxy.addressing.enabled property must be set to false in pg-config.properties and must not be changed.
