By the way, thanks for addressing our issues! MOST of them pass, now.
isXXX failures (TCK bug #4708425):
jaxrpc/ee/w2j/rpc/encoded/marshalltest/(See attached file: Client_MarshallAllStructsTest_from_standalone.jtr)
jaxrpc/ee/w2j/rpc/encoded/marshalltest/(See attached file: Client_MarshallSequenceStructsTest_from_standalone.jtr)
jaxrpc/ee/w2j/rpc/encoded/parametermodetest/(See attached file: Client_InStructTest_from_standalone.jtr)
get/setProperty failures (TCK bug #4708407):
jaxrpc/api/jaxrpc_xml_rpc/Call/(See attached file: Client_SetGetPropertyTest2_from_standalone.jtr)
jaxrpc/api/jaxrpc_xml_rpc/Call/(See attached file: Client_RemovePropertyTest2_from_standalone.jtr)
jaxrpc/api/jaxrpc_xml_rpc/Stub/(See attached file: Client_setPropertyTest5_from_standalone.jtr)
jaxrpc/api/jaxrpc_xml_rpc/Stub/(See attached file: Client_getPropertyTest_from_standalone.jtr)
Two points about the get/setProperty failures:
1. We thought we had agreed that only properties that were in the spec's namespace (ie., javax.xml.rpc..) but not defined by the spec were considered invalid. The Stub test now does this (property name = Constants.INVALID_PROPERTY). The Call tests do not (property name = "UNSUPPORTED_QNAME-PROPERTY").
2. The spec says javax.xml.rpc.JAXRPCException should be thrown for invalid properties. The TCK expects IllegalArgumentException.
Client.class doesn't match Client.java (when recompiled, our test passes):
jaxrpc/ee/j2w/inheritedinterfacetest/(See attached file: Client_inheritedinterfaceTest_from_standalone.jtr)
Russell Butek
[EMAIL PROTECTED]
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:
Subject: Re: TCK Summary with new TCK
Can you send a jtr file which demonstrates the isXXX failure and for your issues on setGetPopertyTest1
thanks
[EMAIL PROTECTED] wrote:
The new TCK resolved a number of issues.
We are still having problems related to the getVarBoolean methods.
(See attached file: TCKIssues.html)
Rich Scheuerle
IBM WebSphere & Axis Web Services Development
512-838-5115 (IBM TL 678-5115)
TCKIssues�
Summary with the new TCK.
Green indicates Tests that are now fixed.
Red indicates failures that we expected would be fixed by the new tck.
�
�
|
|
|
GetPortsPosTest2� |
Note: Axis was changed to pass this test |
* Test is now excluded |
SetGetPropertyTest1_from_standalone |
|
Does Axis need to be changed ? Note that Axis passes but w/ Stub issue |
setPropertyTest5_from_standalone |
|
Does Axis need to be changed ? |
AttachmentsTest_from_standalone |
|
|
inheritedinterfaceTest_from_standalone |
|
The test passes if the Client.java is recompiled. |
MarshallStandardJavaClassesTest_from_standalone |
|
*Fixed |
MarshallJavaBeanTest_from_standalone |
|
* Fixed |
MarshallValueTypeTest_from_standalone |
|
*Fixed |
MarshallJavaArrayTest_from_standalone |
|
*Fixed |
MarshallJavaMultiArrayTest_from_standalone |
|
*Fixed |
MarshallSimpleTypesTest_from_standalone |
|
|
MarshallArraysOfSimpleTypesTest_from_standalone |
11. Calendar issue |
|
SimpleTest_from_standalone |
|
|
invokeStockQuoteService_from_standalone |
|
|
MarshallAllSimpleXMLDataTypeTest_from_standalone |
(Some of the marshal tests also have issues 2 and 11, but they are hidden by 7) |
(TCK bug #4708425 assigned, TCK bug #4714327 assigned) *Fixed |
MarshallAllStructsTest_from_standalone |
|
Why wasn't this issue fixed by the new TCK Do we need to raise this issue again ? |
MarshallSequenceStructsTest_from_standalone |
|
Why wasn't this issue fixed by the new TCK Do we need to raise this issue again ? |
MarshallWSDLRestrictedArrayTest_from_standalone |
|
*Fixed |
MarshallSOAPRestrictedArrayTest_from_standalone |
|
*Fixed |
MarshallExceptionsTest_from_standalone |
|
*Fixed |
MarshallEnumerationsTest_from_standalone |
|
*Fixed |
MarshallAllSimpleXMLDataTypesTest_from_standalone |
|
*Fixed |
InSimpleTypesTest_from_standalone |
|
*Fixed |
OutSimpleTypesTest_from_standalone |
|
*Fixed |
InOutSimpleTypesTest_from_standalone |
|
*Fixed |
InStructTest_from_standalone |
|
Why wasn't this fixed in the TCK ? Do we need to raise this issue again ? |
JavaKeywordsTest_from_standalone |
|
*Fixed |
JavaNamingConventionsTest_from_standalone |
|
*Fixed |
Issue Explanations
Issue: 2 Boolean value
The TCK expects getVarBooloon instead of isVarBoolean for a bean property that is a boolean value.
Issue: 4 getPorts() problem
TCK expects a call to getPorts() to return a null iterator if there is no wsdl.� The specification clearly indicates that an exception should be thrown.� Axis was changed to comply with the TCK.� The Axis change should be backed out once the TCK is fixed.
Issue: 5. Roundtrip Issues
Problems with roundtripping Calendar/Date.
Issue: 6 Wrapped Doc/Lit
The TCK and Axis do not agree on the way to interpret wrapped doc/lit.
�
Issue: 7 Full Bean Constructor
The TCK relies on full constructors in the beans, which is not compliant with the specification.
�
Issue: 8 Stub/Call Get/Set Property Issue
The TCK expects an exception when it sets/gets an unknown property.� AXIS does not throw an exception.
�
Issue: 11 Calendar Issue
The compareCalendars method in the TCK should compare the canonical form of the calendars.
�
Issue: 12 Client.class is stale
The Client.class file for the inherited interface test does not match the Client.java.� Recompiling Client.java fixes the problem.
�
--
Lance Andersen email: [EMAIL PROTECTED]Sun Microsystems Inc. phone: (781) 442-2037
1 Network Drive, UBUR02-301 fax : (781) 442-1610
Burlington, MA 01803
Client_MarshallAllStructsTest_from_standalone.jtr
Description: Binary data
Client_MarshallSequenceStructsTest_from_standalone.jtr
Description: Binary data
Client_InStructTest_from_standalone.jtr
Description: Binary data
Client_SetGetPropertyTest2_from_standalone.jtr
Description: Binary data
Client_RemovePropertyTest2_from_standalone.jtr
Description: Binary data
Client_setPropertyTest5_from_standalone.jtr
Description: Binary data
Client_getPropertyTest_from_standalone.jtr
Description: Binary data
Client_inheritedinterfaceTest_from_standalone.jtr
Description: Binary data
