Web Service Interoperability - Java SOA - page 778

<MessageID xmlns="http://www.w3.org/2005/08/addressing">
uuid:5ea13011-8163-4c03-9d86-dd54159d2165
</MessageID>
<RelatesTo xmlns="http://www.w3.org/2005/08/addressing">
uuid:8c5ff38d-6a7b-477e-8558-2b6572f7ba84
</RelatesTo>
</S:Header>
<S:Body>
<ns2:sayHelloResponse xmlns:ns2="http://soacookbook.com/">
<return>Hello, Eben</return>
</ns2:sayHelloResponse>
</S:Body></S:Envelope>
The SOAP header also includes an addressing Action element. This element has the value
that was indicated by the Action attribute on the web service, like this:
@Action(output = "http://soacookbook.com/greeting")
But of course the client is not reading the Java class; it's examining the WSDL created by that
class, which has the following form:
<portType name="HelloAddressingWS">
<operation name="sayHello">
<input wsaw:Action="http://soacookbook.com/name"
message="tns:sayHello"/>
<output wsaw:Action="http://soacookbook.com/greeting"
message="tns:sayHelloResponse"/>
</operation>
</portType>
You can also see in the response that it includes a <RelatesTo> SOAP header. This header
indicates the value of the universally unique ID that was specified as the value of the <Mes-
sageID> element in the request to which this message is a response.