You are getting me confused... Are you referring to the SOAP request-response MEP? If so, this MEP only relates to the SOAP RPC convention in so far as the RPC convention can use the services of the SOAP request-response MEP. If not, what do you have in mind? Jean-Jacques. James M Snell wrote: > As long as this constraint only affects the RPC binding. It is quite > possible that in a Request/Response message exchange, two messages may > have similarly named parts but do not reflect an in/out parameter. It's > only when the Request/Response MEP is implemented for RPC that this > becomes an issue.Received on Wednesday, 22 May 2002 12:06:09 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:20 GMT