WS-Addressing Reference Properties Confusion

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Fraser Goffin (anonymous_at_discussions.microsoft.com)
Date: 02/23/04

  • Next message: Robert K. Carroll: "WSE SecurityContextToken - ASP.Net Session" 
    Date: Mon, 23 Feb 2004 07:46:07 -0800

    The WS-Addressing spec and schema describe the From, ReplyTo, FaultTo and Recipient headers to be of type EndPointReference :-

    <xs:element name="From" type="wsa:EndpointReferenceType"/><xs:element name="ReplyTo" type="wsa:EndpointReferenceType"/><xs:element name="FaultTo" type="wsa:EndpointReferenceType"/><xs:element name="Recipient" type="wsa:EndpointReferenceType"/

    ... and an EndPointReference type is described as follows :-

    <xs:element name="EndpointReference" type="wsa:EndpointReferenceType"/><xs:complexType name="EndpointReferenceType"><xs:sequence><xs:element name="Address" type="wsa:AttributedURI"/><xs:element name="ReferenceProperties" type="wsa:ReferencePropertiesType" minOccurs="0"/><xs:element name="PortType" type="wsa:AttributedQName" minOccurs="0"/><xs:element name="ServiceName" type="wsa:ServiceNameType" minOccurs="0"/><xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/></xs:sequence><xs:anyAttribute namespace="##other" processContents="lax"/></xs:complexType>

    One could imagine the serialisation of say the ReplyTo element being thus :-

    <ReplyTo xmlns="http://schemas.xmlsoap.org/ws/2003/03/addressing"><Address>myURI</Address><ReferenceProperties/><PortType>Q:name</PortType><ServiceName PortName="NCName">Q:name</ServiceName></ReplyTo>

    Reading on, the spec talks about how when using a SOAP binding the ReferenceProperties should be encoded, in short, each should become independant header blocks.

    My confusion is this....

    Say I want to construct a message which informs the receiver to send in the response a CustomerNo. Should I construct a From header which includes the ReferenceProperty 'CustomerNo' like this ? (i.e. NOT a header block, but part of the From header within ReferenceProperties) : -

    <From xmlns="http://schemas.xmlsoap.org/ws/2003/03/addressing"><Address>senderURI</Address><ReferenceProperties><frg:CustomerNo>abc123</frg:CustomerNo></ReferenceProperties></From>

    such that when the receiver is constructing the response they encode it as :-

    <soap:Envelope xmlns:soap="http://www.w3.org/2002/12/soap-envelope" xmlns:frg="some-uri"><soap:Header><To xmlns="http://schemas.xmlsoap.org/ws/2003/03/addressing">senderURI</To><frg:CustomerNo>abc123</frg:CustomerNo>
        ... other header blocks

    This spec is quite thin on implementation detail (or it might just be me being a bit slow :-), but any help greatly appreciated.

    Regards

    Fraser.

  • Next message: Robert K. Carroll: "WSE SecurityContextToken - ASP.Net Session"

    Relevant Pages

    • Re: Adding elements to the header of a SoapEnvelope
      ... it will get serialized as a header on the request ... If you set the ReplyTo yourself to anonymous role the response would be sent ... back to the client. ... you want to use a header on the request to indicate the address). ...
      (microsoft.public.dotnet.framework.webservices.enhancements)
    • Re: Adding elements to the header of a SoapEnvelope
      ... I don't quite follow the ReplyTo issue. ... request response in WSE. ... > I tried adding a new element to the header of my SoapEnvelope like this: ...
      (microsoft.public.dotnet.framework.webservices.enhancements)
    • Re: header an footer
      ... then one page i want to print its header and footer to each page. ... HTML 4.01 spec: http://www.w3.org/TR/html401/ ... validator: http://jigsaw.w3.org/css-validator/ ...
      (comp.infosystems.www.authoring.html)
    • Adding elements to the header of a SoapEnvelope
      ... I need to provide the service with a piece of infrastructure information, ... namely where to send "events" to during a long-running process. ... I can't use ReplyTo because the reply to the Soap message must be sent to ... I tried adding a new element to the header of my SoapEnvelope like this: ...
      (microsoft.public.dotnet.framework.webservices.enhancements)
    • Re: header an footer
      ... so it makes space for the header. ... afaics this is allowed by the spec: ... "Due to negative margin values ... padding on the body wrapped in a print media rule suffices. ...
      (comp.infosystems.www.authoring.html)