This issue is assigned the number 083. For further
discussions on this issue, please refer to this issue number or use this
thread.
From: Scott de Deugd
[mailto:dedeugd@us.ibm.com]
Sent: Thursday, November 13, 2008 8:05 PM
To: Ram Jeyaraman
Subject: New WSDD Issue: Scope of wsa:ReplyTo
Scope of
wsa:ReplyTo
Document:
wsdd-dpws-1.1-spec-wd-02
Line number: 228
Owner: Scott de Deugd
Description:
Editorial:
Section 3.5
has:
R0031: A
SERVICE MUST generate a wsa:InvalidMessageInformationHeader SOAP Fault if the
[address] of the [reply endpoint] of an HTTP Request Message SOAP ENVELOPE is
not http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous.
This
requirement would prevent implementations from using other values which may be
necessary in some situations. For example, this would prevent an
asynchronous response (if needed for long-running operations) or even other
anonymous-like values (e.g. WS-MakeConnection's anonymous URI). However,
as a baseline having support for wsa:Anonymous would be a good thing for
interoperability. So, turning this requirement around and rather than
forcing one particular value we could simply make sure that services support at
least wsa:Anonymous.
Proposed Resolution (changes in red):
R0031: A SERVICE MUST NOT generate a
wsa:InvalidMessageInformationHeader SOAP Fault if the [address] of the [reply
endpoint] of an HTTP Request Message SOAP ENVELOPE is not "http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous".