- From: Marc Hadley via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 02 Jun 2005 18:56:39 +0000
- To: public-ws-addressing-eds@w3.org
Update of /sources/public/2004/ws/addressing
In directory hutz:/tmp/cvs-serv28540
Modified Files:
ws-addr-soap.xml
Log Message:
Added resolution to issue lc73 - added note warning about use of reference parameters conflicting with normal message semantics
Index: ws-addr-soap.xml
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-soap.xml,v
retrieving revision 1.74
retrieving revision 1.75
diff -C2 -d -r1.74 -r1.75
*** ws-addr-soap.xml 2 Jun 2005 18:15:28 -0000 1.74
--- ws-addr-soap.xml 2 Jun 2005 18:56:37 -0000 1.75
***************
*** 344,347 ****
--- 344,355 ----
[in-scope namespaces]) is added as a SOAP header block in
the new message.</p>
+ <note><p>The insertion of SOAP headers into a message implies particular
+ semantics. Since the reference parameter mechanism does not restrict
+ the content of the generated headers, EPR suppliers should exercise
+ appropriate caution to ensure their reference parameters do not cause
+ unintended or erroneous semantics in the resultant SOAP message. For
+ example, using a reference parameter to send a WS-Security<bibref ref="WS-Security"/> header would
+ be ill-advised (since other parts of the SOAP infrastructure will often
+ control this header, and there must be at most one of them per message).</p></note>
</item>
<item>
Received on Thursday, 2 June 2005 18:56:49 UTC