Web Services

SOAP 1.2 Implementation Summary

The purpose of the information contained on this page is to document the evidence of interoperable implementations required to advance the SOAP 1.2 specification. See the status section of the specification, e.g. http://www.w3.org/TR/2002/WD-soap12-part0-20020626/ for details of these requirements.

Page contents:

• Implementations
• Features
• Additional Tests
• Stale Features

Table 1: Implementation Listing

Table 2 lists the features, evidence of feature implementations, and test(s) associated with each feature. There is no association between the numbers used in identifying the implementation columns and the implementations listed in Table 1.

Table 2: Implementation Coverage of SOAP 1.2 Features

Table notes:

• In Implementation col 2, Y' indicates the feature is supported and is testable via an endpoint, Y indicates the feature is supported although no test exists at the endpoint
• Rows representing features colored yellow have <2 supporting implementations and/or a missing test.
• [1] Meetings of implementers held 31 July, 1 August and 8 August 2002.
• [2] Implementer meeting held 14 Nov 2002
• SOAPBuilders' tests that have been considered for the tests: Round 1, Round 2, Round 3, Round 4
• [3] Implementer meeting held 25 Nov 2002

Proposed Intermediary Tests Here is a proposal for how to test the functionality of an intermediary for the purpose of testing the SOAP intermediary processing, not the relaying to another node.

General Test Setup We use a single HTTP request/response for doing the R4 "echoString" test. The HTTP request contains a SOAP message that is to be forwarded by the SOAP receiver on the HTTP server. However, rather than actually forwarding the message, the HTTP server returns what would have been the forwarded message in the HTTP response. That is, the HTTP response contains the "forwarded" message. In other words, the message path is

        A --> B --> A

where the initial sender and the ultimate receiver is the same node. Nothing of course prevents this in any real system.

The test would be similar to an "echoString" function, but instead of "echoString", the response is the result of the SOAP 1.2 forwarding semantics. This allows us to test intermediaries using the existing HTTP binding and with the existing SOAP request response MEP.

Table 2: Additional Tests

Table 4 lists features that were once in Table 2 but have subsequently been superseded, modified or deleted. The Notes on Table 2 should apply to all entries in Table 4.

Table 4: Stale SOAP 1.2 Features

David Fallside, Yves Lafon
$Id: soap1.2implementation.html,v 1.23 2002/11/25 23:31:00 dcf Exp $