Which of the following SOAP headers in the request message convey the intention? Assume the endpoint reference of Service S is

In the following situation, Client C sends a SOAP request to Service S and the response is to be processed by a third party response processor R. Which of the following SOAP headers in the request message convey the intention? Assume the endpoint reference of Service S is

In the following situation, Client C sends a SOAP request to Service S and the response is to be processed by a third party response processor R. Which of the following SOAP headers in the request message convey the intention? Assume the endpoint reference of Service S is

A.
<s11:Header>
<wsa:Action>http://example.com/action/process</wsa:Action> <wsa:ReplyTo>
<wsa:Address>http://www.w3.org/2005/08/addressing/none</wsa:Address> <wsa:ReplyTo>
</s11:Header>

B.
<s11:Header>
<wsa:Action>http://example.com/action/process</wsa:Action> <wsa:ReplyTo>
<wsa:Address>http://www.w3.org/2005/08/addressing/anonymous</wsa:Address> <wsa:ReplyTo>
</s11:Header>

C.
<s11:Header>
<wsa:Action>http://example.com/action/process</wsa:Action> <wsa:ReplyTo>
<wsa:Address>http://example.com/responseprocessor</wsa:Address> <wsa:ReplyTo>
</s11:Header>

D.
<s11:Header>
<wsa:Action>http://example.com/action/process</wsa:Action> <wsa:ReplyTo>
<wsa:Address>http://example.com/service</wsa:Address> <wsa:ReplyTo>
</s11:Header>

Show Hint

Leave a Reply 2

Your email address will not be published. Required fields are marked *

leo yu

leo yu

exam point: WS-addressing, Endpoint reference, Action, From, ReplyTo…
http://www.ibm.com/developerworks/library/ws-address/

Comparatively, JAX-RS is simpler to handle the resource addressing than JAX-WS in that the JAX-RS is only over HTTP, thus the resource could be identified with the query string.

Which implementation like Axis has the best implementation of ws-addressing?

Reply

Mohamed Fayek Saber

Mohamed Fayek Saber

Web Services Addressing 1.0 – Core

https://www.w3.org/TR/ws-addr-core/

This specification defines a family of message addressing properties that convey end-to-end message characteristics including references for source and destination endpoints and message identity that allows uniform addressing of messages independent of the underlying transport.
Both of these constructs are designed to be extensible and re-usable so that other specifications can build on and leverage endpoint references and message addressing properties.

The following example illustrates the use of these mechanisms in a SOAP 1.2 message being sent from http://example.com/business/client1 to http://example.com/fabrikam/Purchasing (see Web Services Addressing 1.0 – SOAP Binding[WS-Addressing SOAP Binding] for more information on the use of WS-Addressing in SOAP):

Example 1-1. Use of message addressing properties in a SOAP 1.2 message.
(01)
(02)
(03) http://example.com/6B29FC40-CA47-1067-B31D-00DD010662DA
(04)
(05) http://example.com/business/client1
(06)
(07) http://example.com/fabrikam/Purchasing
(08) http://example.com/fabrikam/SubmitPO
(09)
(10)
(11) …
(12)
(13)

Lines (02) to (09) represent the header of the SOAP message where the mechanisms defined in the specification are used. The body is represented by lines (10) to (12).
Lines (03) to (08) contain the message addressing header blocks. Specifically, line (02) specifies the identifier for this message and lines (04) to (06) specify the endpoint to which replies to this message should be sent as an endpoint reference. Line (07) specifies the address URI of the ultimate receiver of this message. Line (08) specifies an action URI identifying expected semantics.

Reply