- From: Henrik Frystyk Nielsen <henrikn@microsoft.com>
- Date: Mon, 25 Nov 2002 15:53:50 -0800
- To: "Paul Kulchenko" <paulclinger@yahoo.com>, "David Fallside" <fallside@us.ibm.com>, "John Koropchak" <johnko@microsoft.com>, "Don Mullen" <donmullen@tibco.com>
- Cc: <xml-dist-app@w3.org>
Ok, sounds good. Henrik Frystyk Nielsen mailto:henrikn@microsoft.com >-----Original Message----- >From: Paul Kulchenko [mailto:paulclinger@yahoo.com] >Sent: Monday, November 25, 2002 15:50 >To: Henrik Frystyk Nielsen; David Fallside; John Koropchak; Don Mullen >Cc: xml-dist-app@w3.org > >> 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? >That's very close to what I have in mind, however, it seems >like R2.echoSimpleTypesAsStruct [4] will work better for this >test (echoStructAsSimpleTypes accepts only one parameter, >whereas echoSimpleTypesAsStruct accepts three). So, if instead >of sending > ><m:echoSimpleTypesAsStruct xmlns:m="http://soapinterop.org/"> > <inputString>hello world</inputString> > <inputInteger>42</inputInteger> > <inputFloat>0.005</inputFloat> ></m:echoSimpleTypesAsStruct> > >client sends > ><m:echoSimpleTypesAsStruct xmlns:m="http://soapinterop.org/"> > <inputString>hello world</inputString> > <inputInteger>42</inputInteger> ></m:echoSimpleTypesAsStruct> > >and then server will either respond as in [4] or return fault >as described above. > >Best wishes, Paul. > >[4] >http://www.whitemesa.com/interop/proposalB.html#echoSimpleTypesAsStruct > >--- Henrik Frystyk Nielsen <henrikn@microsoft.com> wrote: >> >> 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:54:24 UTC