- From: Jacek Kopecky <jacek@systinet.com>
- Date: 26 Nov 2002 18:16:26 +0100
- To: XMLP Dist App <xml-dist-app@w3.org>, David Fallside <fallside@us.ibm.com>
Per my action item, below are the proposed tests for features 60.? - testing RPC BadArguments and RPC ProcedureNotPresent faults. I think this covers my AIs. Share and enjoy, Jacek Kopecky Senior Architect, Systinet Corporation http://www.systinet.com/ (Feature 60.?) Sender/BadArguments We use R1.echoInteger test [5] as the basis for this test. Instead of sending a proper integer value the Node A sends string instead: <m:echoInteger xmlns:m="http://soapinterop.org/"> <inputInteger>ouch!</inputInteger> </m:echoInteger> The Node C returns a fault with a value env:Sender for Code, a value of rpc:BadArguments for Subcode. [5] http://www.whitemesa.com/interop/proposal2.html#echoInteger (Feature 60.other?) Sender/ProcedureNotPresent We use R1.echoInteger test [5] as the basis for this test, too. Instead of sending a proper echoInteger call the Node A sends unknownMethodThatShouldNotBeThere instead: <m:unknownMethodThatShouldNotBeThere xmlns:m="http://soapinterop.org/"/> The Node C returns a fault with a value env:Sender for Code, a value of rpc:ProcedureNotPresent for Subcode.
Received on Tuesday, 26 November 2002 12:16:30 UTC