27.01.2014 Views

SOAP Version 1.2 Specification Assertions and Test Collection

SOAP Version 1.2 Specification Assertions and Test Collection

SOAP Version 1.2 Specification Assertions and Test Collection

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Comments<br />

based on a <strong>SOAP</strong>/1.1 message construct. That is, the envelope will<br />

have a [local name] of Envelope <strong>and</strong> a [namespace name] of<br />

"http://schemas.xmlsoap.org/soap/envelope/".<br />

2. A <strong>SOAP</strong> <strong>Version</strong> <strong>1.2</strong> node receiving a <strong>SOAP</strong>/1.1 message either:<br />

" MAY process the message as a <strong>SOAP</strong>/1.1 message (if<br />

supported), or<br />

" MUST generate a version mismatch <strong>SOAP</strong> fault based on a<br />

<strong>SOAP</strong>/1.1 message construct following <strong>SOAP</strong>/1.1 semantics<br />

using a <strong>SOAP</strong>/1.1 binding to the underlying protocol (see<br />

[soap11]). The <strong>SOAP</strong> fault SHOULD include an Upgrade <strong>SOAP</strong><br />

header block as defined in this specification (see 5.4.7<br />

<strong>Version</strong>Mismatch Faults) indicating support for <strong>SOAP</strong> <strong>Version</strong><br />

<strong>1.2</strong>. This allows a receiving <strong>SOAP</strong>/1.1 node to correctly interpret<br />

the <strong>SOAP</strong> fault generated by the <strong>SOAP</strong> <strong>Version</strong> <strong>1.2</strong> node.<br />

The requirement on the behavior of <strong>SOAP</strong> 1.1 compliant <strong>SOAP</strong> node will not be tested<br />

by the test collection.<br />

<strong>Test</strong>s<br />

T30<br />

2.2 <strong>SOAP</strong> <strong>1.2</strong>, Part 2 <strong>Assertions</strong><br />

Assertion x2-values-struct<br />

Location of the assertion<br />

<strong>SOAP</strong> <strong>1.2</strong> Part 2, Section 2.3<br />

Text from the specification<br />

A graph node whose outbound edges are distinguished solely by their<br />

labels is known as a "struct". The outbound edges of a struct MUST be<br />

labeled with distinct names (see 2.1.1 Edge labels).<br />

Assertion x2-values-array<br />

Location of the assertion<br />

<strong>SOAP</strong> <strong>1.2</strong> Part 2, Section 2.3<br />

From www.w3c.org 43 7/10/2003

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!