Testing Tools Version 1.0.1 Known Issues

Working Group Draft

Date: 2004/02/05 15:04:35.01

This revision:

http://www.ws-i.org/Testing/Tools/2004/02/Testing_Tools_1.00.01_Known_Issues.htm

Editors:

Jacques Durand, Fujitsu
Ed Johns, Microsoft.
David Lauzon, IBM

Administrative Contact:

secretary@ws-i.org

Notice

The material contained herein is not a license, either expressly or impliedly, to any intellectual property owned or controlled by any of the authors or developers of this material or WS-I. The material contained herein is provided on an "AS IS" basis and to the maximum extent permitted by applicable law, this material is provided AS IS AND WITH ALL FAULTS, and the authors and developers of this material and WS-I hereby disclaim all other warranties and conditions, either express, implied or statutory, including, but not limited to, any (if any) implied warranties, duties or conditions of merchantability, of fitness for a particular purpose, of accuracy or completeness of responses, of results, of workmanlike effort, of lack of viruses, and of lack of negligence. ALSO, THERE IS NO WARRANTY OR CONDITION OF TITLE, QUIET ENJOYMENT, QUIET POSSESSION, CORRESPONDENCE TO DESCRIPTION OR NON-INFRINGEMENT WITH REGARD TO THIS MATERIAL.

IN NO EVENT WILL ANY AUTHOR OR DEVELOPER OF THIS MATERIAL OR WS-I BE LIABLE TO ANY OTHER PARTY FOR THE COST OF PROCURING SUBSTITUTE GOODS OR SERVICES, LOST PROFITS, LOSS OF USE, LOSS OF DATA, OR ANY INCIDENTAL, CONSEQUENTIAL, DIRECT, INDIRECT, OR SPECIAL DAMAGES WHETHER UNDER CONTRACT, TORT, WARRANTY, OR OTHERWISE, ARISING IN ANY WAY OUT OF THIS OR ANY OTHER AGREEMENT RELATING TO THIS MATERIAL, WHETHER OR NOT SUCH PARTY HAD ADVANCE NOTICE OF THE POSSIBILITY OF SUCH DAMAGES.

Feedback

If there are areas in this specification that could be clearer, or if errors or omissions are identified, WS-I would like to be notified in order to provide the best possible interoperability guidance.

By sending email, or otherwise communicating with WS-I, you (on behalf of yourself if you are an individual, and your company if you are providing Feedback on behalf of the company) will be deemed to have granted to WS-I, the members of WS-I, and other parties that have access to your Feedback, a non-exclusive, non-transferable, worldwide, perpetual, irrevocable, royalty-free license to use, disclose, copy, license, modify, sublicense or otherwise distribute and exploit in any manner whatsoever the Feedback you provide regarding the work. You acknowledge that you have no expectation of confidentiality with respect to any Feedback you provide. You represent and warrant that you have rights to provide this Feedback, and if you are providing Feedback on behalf of a company, you represent and warrant that you have the rights to provide Feedback on behalf of your company. You also acknowledge that WS-I is not required to review, discuss, use, consider or in any way incorporate your Feedback into future versions of its work. If WS-I does incorporate some or all of your Feedback in a future version of the work, it may, but is not obligated to include your name (or, if you are identified as acting on behalf of your company, the name of your company) on a list of contributors to the work. If the foregoing is not acceptable to you and any company on whose behalf you are acting, please do not provide any Feedback.

Feedback on this document should be directed to wsi-tools@ws-i.org.

Status of this Document

This document is a Working Group Draft; it has been accepted by the Working Group as reflecting the current state of discussions. It is a work in progress, and should not be considered authoritative or final; other documents may supersede this document.

is001	Analyzers: different processing on XML encoding
	Description There are some cases in which an encoding specified in the XML declaration of a WSDL or schema document will be recognized by one analyzer, but not by the other. For example, the encoding cp125 is not recognized by the C# analyzer but will be accepted by the Java analyzer. In this case the C# analyzer will fail more assertions than the Java analyzer (however, the Java analyzer will fail assertion WSI2201). An analogous situation would occur in the case where the C# analyzer recognized an encoding but the Java analyzer did not. Resolution: 2003-10-16 Severity: low. This problem does not affect the consistency of the final reports: the material under test will fail to conform with both tools, just in different ways. An encoding problem will cause an XML parsing error, which in turns prevents the Analyzer to complete its analysis. In such a case, users should consider the possibility of an encoding failure.
is002	Analyzers: processing differences on test assertions WSI1011 and WSI1013
	Description There is one portion of the WSI1011 and WSI1013 test assertions that is not implemented in the Java analyzer. The Java analyzer does not schema validate the contents of a SOAP message when processing these test assertions. This means that the Java analyzer may return a passed result instead of a failed result when the message content does not match the schema definition. Resolution: 2003-10-23 Severity: medium. This problem will result in Java reports that are overly optimistic. Note however, apart from schema-validation all the remaining correlation cross-checking between a wsdl document and candidate message is done without using the schema validator. Next tool release will address this problem.
is003	Java Analyzer: does not check for invalid DOCTYPE in test assertion WSI1701
	Description When a message contains an invalid DOCTYPE statement, the Java analyzer will return a passed result when it should return a failed result. Resolution: 2003-09-16 Severity: medium. This situation is not commonly expected. Scheduled for next maintenance release of Tools.
is005	Analyzers: processing differences on test assertion WSI1116
	Description Message parts that reference a non-existent type prevent the C# analyzer from determining the operation signature for the message. In this case the C# analyzer will return a notApplicable where the Java analyzer may return a result of pass. Resolution: 2003-09-16 Severity: low.
is006	Analyzers: processing differences on test assertions WSI1701, WSI2201
	Description C# analyzer may return fail (and its dependant assertions to return results of notAapplicable), in cases where the Java analyzer returns a pass. This occurs because the code in C# analyzer which validates schema against the XML schema for schemas will generate an error if the schema being validated contains a reference to an undefined complex type. Resolution: 2003-09-16 Severity: medium. This is directly related to issue is002 above.
is008	C# Analyzer: config errors not trapped
	Description Due to a known issue in the V1.1 .NET libraries, errors in the analyzer configuration file related to the wsdlElement and uddiKey elements XML are not trapped. Resolution: 2003-10-21 Priority: medium. Scheduled for when .NET library will be fixed.
is010	C# Analyzer: WSI1701 fails instead of WSI1204
	Description Schema which contain types based on soapenc:Array will cause assertion WSI1701 (conformance to the SOAP schema) to fail, instead of WSI1204 (soap:body does not contain the soapenc:arrayType attribute) Resolution: 2003-10-21 Severity: low.
is011	Analyzers: processing differences on test assertion WSI2122
	Description When processing test assertion WSI2122, the C# analyzer actually schema validates the data type definitions within the WSDL document, while the Java analyzer validates them against the schema for XML Schemas (XML Schema 1.0 Recommendation with namespace "http://www.w3.org/2001/XMLSchema"). This means that the Java analyzer, because it does not fully check the data type definitions themselves, may return a passed result even though these definitions may be invalid. Resolution: 2004-01-22 Severity: medium. This problem will result in Java reports that may be overly optimistic. Next tool release will address this problem.
is012	C# Analyzer: WSI1701 fails instead of WSI1011, WSI1013 or WSI1009
	Description If the schemas in the WSDL Types section contain certain errors, such as types multiply defined, these errors will cause assertion WSI1701 to fail, instead of more relevant assertions such as WSI1011, WSI1013 or WSI1009 Resolution: 2004-01-27 Severity: medium. Next tool release will address this problem.