Web Services Architecture and Its Specifications [Electronic resources] : Essentials for Understanding WS-* نسخه متنی

Addressing Resources

Each of the drinking fountains can be addressed directly, even if requests are routed through a Resource Manager and Agents. In our example system, the URIs of the Agent and Resource Service, as well as the identifiers for each fountain, are listed here:

Agent http://control.fineartschool.com/facilities

Resource Service http://control.fineartschool.com/fountains

Fountain IDs b42f3North, b19f1Cafe, b2f1Lobby

When using WS-Addressing to send management messages for these resources, the SOAP addressing header block is as shown here:

Addressing Resources
(01)  <env:Header>
...
(02)   <wsa:To>http://control.fineartschool.com/facilities</wsa:To>
(03)   <wsman:ResourceURI>
(04)       http://control.fineartschool.com/fountains
(05)   </wsman:ResourceURI>
(06)   <wsman:Key Name="ResourceID">b42f3North</wsman:Key>
(07)  </env:Header>

Line 02 The Agent URI is used as the message's To address.

Lines 0305 The URI of the resourcein this case, the agent for managing the drinking fountainsis included. When bootstrapping clients, this information may have been communicated in an endpoint reference.

Line 06 In our example, we identify each resource by using the Key element. When the Name attribute is set to ResourceID, the example system uses the element value as the identifier for the specific resource being managed.