- From: Anish Karmarkar <Anish.Karmarkar@oracle.com>
- Date: Mon, 31 Jul 2006 15:25:53 -0700
- To: "public-ws-addressing@w3.org " <public-ws-addressing@w3.org>
Title: What happens when the soapAction value is specified in WSDL but is not an absolute URI Spec: WSDL binding Description: WS-A Action property is an absolute URI, but SOAPAction HTTP header is not necessarily an absolute URI. We have said in the SOAP binding doc that the WS-A Action property value must match that of the SOAPAction HTTP header value unless the SOAPAction HTTP header is "". The spec is silent on what happens when there is a non-empty non-absolute URI specified for SOAPAction when used with WS-Addressing engaged. Such a value for wsa:Action is not allowed, since it is not an absolute URI, but having a valid value for wsa:Action would mean violating the requirement that the two values be the same (unless SOAPAction is ""). Suggested solution: We could either remove the requirement that the two values be the same (unless SOAPAction is "") OR make such WSDL description incorrect/not valid. Given that the requirement for the two values to be the same (unless SOAPAction is "") is in the SOAP binding spec -- which is a REC -- not allowing something like this in WSDL is the easiest thing to do to fix this problem. Comments? -Anish --
Received on Monday, 31 July 2006 22:26:32 UTC