- From: Anish Karmarkar <Anish.Karmarkar@oracle.com>
- Date: Tue, 11 Oct 2005 16:30:20 -0700
- To: xmlp-comments@w3.org
- CC: Shih-Chang Chen <shih-chang.chen@oracle.com>, "Tim. Julien@oracle. com" <Tim.Julien@oracle.com>, Bill Jones <BILL.JONES@oracle.com>
XMLPers, Our implementation team came across two bugs in SOAP 1.2 Specification Assertions and Test Collection document: Tests T27 [1] and T58 [2] consists of node A sending a message that contains an incorrect type/value. Test 27 contains an array with declared itemType of xs:string but contains a complex type. Test T58 contains an array with declared itemType of xs:int but contains a complex type. SOAP 1.2 part 2, section 4.4 [3] says: "A fault with a Value of Code set to "env:Sender" and a Value of Subcode set to "rpc:BadArguments" MUST be generated when the receiver cannot parse the arguments or when there is a mismatch in number and/or type of the arguments between what the receiver expects and what was sent." But both tests T27 and T58 do not have a Subcode in the fault sent from node C to node A. Note that test XMLP-11 [4] consists of a similar situation and node C sends the correct fault Subcode (rpc:BadArguments). For implementations to consistently and correctly generate Fault Subcodes, I would like to suggest that T27 and T58 be modified to include the following Fault Subcode in the message from node C to node A: ----- <env:Subcode> <env:Value xmlns:rpc="http://www.w3.org/2003/05/soap-rpc"> rpc:BadArguments </env:Value> </env:Subcode> ----- Thanks. -Anish -- [1] http://www.w3.org/TR/2003/REC-soap12-testcollection-20030624/#T27 [2] http://www.w3.org/TR/2003/REC-soap12-testcollection-20030624/#T58 [3] http://www.w3.org/TR/2003/REC-soap12-part2-20030624/#rpcfaults [4] http://www.w3.org/TR/2003/REC-soap12-testcollection-20030624/#XMLP-11
Received on Tuesday, 11 October 2005 23:30:36 UTC