W3C home > Mailing lists > Public > xmlp-comments@w3.org > June 2002

RE: SOAP 1.2 Test Suite feedback

From: Henrik Frystyk Nielsen <henrikn@microsoft.com>
Date: Wed, 5 Jun 2002 11:58:00 -0700
Message-ID: <79107D208BA38C45A4E45F62673A434D07D01B91@red-msg-07.redmond.corp.microsoft.com>
To: "Anish Karmarkar" <Anish.Karmarkar@oracle.com>, <w3c-xml-protocol-wg@w3.org>
Cc: <xmlp-comments@w3.org>, "Ramesh Seshadri" <ramesesh@microsoft.com>, "Paul Cotton" <pcotton@microsoft.com>, "Alex DeJarnatt" <alexdej@microsoft.com>, "Kirill Gavrylyuk" <kirillg@microsoft.com>


Thanks for the review,

>> * Test:T1.4.2
>> 
>> Is the assertion in the description correct ?
>> 
>
>Hmm. This test got added as a result of resolution of issue 194, which
>says that:
>"The encoding style attribute MUST NOT appear in ANY element defined in
>the envelope namespace"

I think it has been changed to where it MAY appear rather than where it
MUST NOT appear. It might have been clearer by saying where it MUST NOT
appear but I can go either way.

>> * 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.
>> 
>
>That is quite true. The test collection does a lot of things that are
>not required (RPC, soap encoding are optional), but aid interop
>implementations. It seems to me that this test would aid interop
>implementations.

This IMO this should be clearly marked and alternatives at least called
out.

>> * 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.
>> 
>
>'yes' will be changed to 'true'.

No, 'yes' was correct, it was a spec bug (which has been fixed).

>> * Test:encodingStyle-on-env-test
>> 
>> It is not clear what assertion is being tested by this test.
>
>This test got added as a result of resolution of issue 194, which says
>that:
>"The encoding style attribute MUST NOT appear in ANY element defined in
>the envelope namespace"
>
>But I do not see this text in the latest spec.
>Is this an issue against the spec?

Same as comment above - encodingStyle can not appear on elements
directly defined by envelope schema.

>> Proposal for some additions to the test suite
>> ---------------------------------------------
>> 
>> * May want to add a test for Nested Structs.
>> 
>
>I think that this is a good idea. I believe SOAP builders 
>round 2 (base)
>has a echoStruct test. This can be ported to SOAP 1.2
>
>> * When unsupported Content-Type is sent, the response should 
>be that of
>> Http Error 415.
>
>Good idea. Will be added.
>
>> 
>> * When the request for an array doesn't explicitly mention 
>an ItemType
>> attribute in it, the server should be able to handle the response.
>> 
>
>A test for this scenario will be added.

Great - thanks!

Henrik
Received on Wednesday, 5 June 2002 14:58:33 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 08:42:27 GMT