- From: Henrik Frystyk Nielsen <henrikn@microsoft.com>
- Date: Tue, 4 Jun 2002 13:53:47 -0700
- To: <xmlp-comments@w3.org>
- Cc: <w3c-xml-protocol-wg@w3.org>, "Ramesh Seshadri" <ramesesh@microsoft.com>, "Paul Cotton" <pcotton@microsoft.com>, "Alex DeJarnatt" <alexdej@microsoft.com>, "Kirill Gavrylyuk" <kirillg@microsoft.com>
Microsoft has these initial comments against the test suite revision found at [1]. More comments may follow at a later time. Feedback on specific tests -------------------------- * Test:T1.2.25 The description says that the NodeC should return one MustUnderstand Fault. But the message doesn't have a Fault in it. * Test:T1.3.1 The Response message (from Node C) has an additional namespace for soap-faults (xmlns:f="http://www.w3.org/2001/12/soap-faults"), which is not required nor is used. * Test:T1.3.2 The Description say that Node C returns a DTDNotSupported Exception. This is incorrect as the latest spec has no mention of such exception but rather a note [4] explaining that "a binding that accepts XML 1.0 serializations MUST fault in a binding specific manner if an XML 1.0 serialization corresponding to a DTD for the SOAP message is received.". * Test:T1.4.1 The Description talks about an element with attribute enc:arrayType="xs:int[3]". ArrayType doesn't exist in Soap 1.2 spec. * Test:T1.4.2 Is the assertion in the description correct ? * Test:Mark84 Description says NodeC returns a VersionMisMatch fault. However, SOAP 1.1 implementations over HTTP are likely to fail on the missing SOAPAction HTTP header field before even starting on the SOAP processing. In this case, a SOAP fault may not be returned. * Test:Mark138 what assertion does this test ? * Test:Mark142 This test shows the generation of a rpc:ProcedureNotPresent fault subcode but this is not required anymore (it is a MAY). Hence this response is not guaranteed. An equally valid response would not have this subcode. * Test:LRT102 The request is missing a Closing Header Element tag. * Test:LRT103 & Test:LRT102 These 2 tests appear to be identical. They have the same description. * Test:LRT104 The request/response message doesn't match the Description. * Test:notation-test & Test:entity-test We don't specify DTDNotSupported anymore. * Test:standalone-test The request message has standalone='yes', this corresponds to XML 1.0 [2], but SOAP 1.2 specifies "true" [3]. This has been reported to the SOAP 1.2 spec editors as a bug. * Test:trailer-test & Test:no-body-test & Test:non-nsqualified-attr-test The request message uses "Head" element instead of "Header" element. * Test:encodingStyle-on-env-test It is not clear what assertion is being tested by this test. Proposal for some additions to the test suite --------------------------------------------- * May want to add a test for Nested Structs. * When unsupported Content-Type is sent, the response should be that of Http Error 415. * When the request for an array doesn't explicitly mention an ItemType attribute in it, the server should be able to handle the response. [1] http://www.w3.org/2000/xp/Group/2/03/11/soap-1.2-conformance.html [2] http://www.w3.org/TR/REC-xml.html#sec-rmd [3] http://www.w3.org/2000/xp/Group/2/05/31/soap12-part1-1.128.html#soapenv [4] http://www.w3.org/2000/xp/Group/2/05/31/soap12-part1-1.128.html#bindfw
Received on Tuesday, 4 June 2002 16:53:58 UTC