- From: Henrik Frystyk Nielsen <henrikn@microsoft.com>
- Date: Mon, 25 Nov 2002 15:20:28 -0800
- To: "David Fallside" <fallside@us.ibm.com>, "John Koropchak" <johnko@microsoft.com>, "Don Mullen" <donmullen@tibco.com>, "Paul Kulchenko" <paulclinger@yahoo.com>
- Cc: <xml-dist-app@w3.org>
In response to an action item regarding providing a test case for implementation feature 54 (see table 2 in [3]), here is a proposed test: We use R2.echoStructAsSimpleTypes [1] as the basis for the test as follows: The sample input is described in [1] as <complexType name="SOAPStruct"> <complexContent> <all> <element name="varString" type="xsd:string"/> <element name="varInt" type="xsd:int"/> <element name="varFloat" type="xsd:float"/> </all> </complexContent> </complexType> But rather than sending, say: <ExampleStruct> <varString>Hello</varString> <varInt>8</varInt> <varFloat>10.2</varFloat> </ExampleStruct> then the client OMITS one parameter, say: <ExampleStruct> <varString>Hello</varString> <varInt>8</varInt> </ExampleStruct> The result is either as in [1] but with the missing input parameter missing in the output as well OR a SOAP fault with a Value of "env:Sender" for Code and a Value of "rpc:BadArguments" for Subcode. Comments? Henrik Frystyk Nielsen mailto:henrikn@microsoft.com [1] http://www.whitemesa.com/interop/proposalB.html#echoStructAsSimpleTypes [2] http://www.w3.org/2000/xp/Group/2/06/LC/soap12-part2.html#rpcfaults [3] http://www.w3.org/2000/xp/Group/2/03/soap1.2implementation.html
Received on Monday, 25 November 2002 18:21:01 UTC