sun.com docs.sun.com | My Sun Worldwide Sites

|  | Products |  | Downloads |  | Service & Solutions |  | Support |  | Training |  | Research

| Previous Contents Next
### 2.2.3 SOAP with Attachments API for Java 1.3 Test Appeals Process Sun has a well established process for managing challenges to its Java technology Test Suites and plans to continue using a similar process in the future. Because SOAP with Attachments API for Java 1.3 requires one or more subcomponent TCKs, the SOAP with Attachments API for Java 1.3 test appeals process will be consistent with the existing subcomponent TCK test appeals processes. Sun, as SOAP with Attachments API for Java 1.3, will authorize representatives from the Java Licensee Engineering group to be the point of contact for all test challenges. Typically this will be the engineer assigned to a company as part of its SOAP with Attachments API for Java TCK support. If a test is determined to be invalid in function or if its basis in the specification is suspect, the test may be challenged by any licensee of the SOAP with Attachments API for Java TCK. Each test validity issue must be covered by a separate test challenge. Test validity or invalidity will be determined based on its technical correctness such as: Test has bugs (i.e., program logic errors) Specification item covered by the test is ambiguous Test does not match the specification Test assumes unreasonable hardware and/or software requirements Test is biased to a particular implementation Challenges based upon issues unrelated to technical correctness as defined by the specification will normally be rejected. Test challenges must be made in writing to Java Licensee Engineering and include all relevant information as described in the Test Challenge Form. The process used to determine the validity or invalidity of a test (or related group of tests) is described in "SOAP with Attachments API for Java TCK Test Appeals Steps." All tests found to be invalid will either be placed on the Exclude List for that version of the SOAP with Attachments API for Java TCK or have an alternate test made available. Tests that are placed on the Exclude List will be placed on the Exclude List within one business day after the determination of test validity. The new Exclude List will be made available to all SOAP with Attachments API for Java TCK licensees on the SOAP with Attachments API for Java TCK Web site. Sun, as Maintenance Lead has the option of creating alternative tests to address any challenge. Alternative tests (and criteria for their use) will be made available on the SOAP with Attachments API for Java TCK Web site. Note - Passing an alternative test is deemed equivalent to passing the original test. #### SOAP with Attachments API for Java TCK Test Appeals Steps SOAP with Attachments API for Java TCK licensee writes a test challenge to Java Licensee Engineering contesting the validity of one or a related set of SOAP with Attachments API for Java 1.3 tests. A detailed justification for why each test should be invalidated must be included with the challenge as described by the Test Challenge Form. Java Licensee Engineering evaluates the challenge. If the appeal is incomplete or unclear, it is returned to the submitting licensee for correction. If all is in order, Java Licensee Engineering will check with the responsible test developers to review the purpose and validity of the test before writing a response as described by the Test Challenge Response Form. Java Licensee Engineering will attempt to complete the response within 5 business days. If the challenge is similar to a previously rejected test challenge (i.e., same test and justification), Java Licensee Engineering will send the previous response to the licensee. The challenge and any supporting materials from test developers is sent to the specification engineers for evaluation. A decision of test validity or invalidity is normally made within 15 working days of receipt of the challenge. All decisions will be documented with an explanation of why test validity was maintained or rejected. The licensee is informed of the decision and proceeds accordingly. If the test challenge is approved and one or more tests are invalidated, Sun places the tests on the Exclude List for that version of the SOAP with Attachments API for Java TCK (effectively removing the test(s) from the Test Suite). All tests placed on the Exclude List will have a bug report written to document the decision and made available to all licensees through the bug reporting database. If the test is valid but difficult to pass due to hardware or operating system limitations, Sun may choose to provide an alternate test to use in place of the original test (all alternate tests are made available to the licensee community). If the test challenge is rejected, the licensee may choose to escalate the decision to the Executive Committee (EC), however, it is expected that the licensee would continue to work with Sun to resolve the issue and only involve the EC as a last resort. #### 2.2.3.1 Test Challenge Form Provide the following information to Java Licensee Engineering:
    Test Challenger Name and Company:
    Specification Name(s) and Version(s):
    Test Suite Name and Version:
    Exclude List Version:
    Test Name:
    Complaint (argument for why test is invalid):
#### 2.2.3.2 Test Challenge Response Form Provide the following information in response to a test challenge.
    Test Defender Name and Company:
    Test Defender Role in Defense (e.g., test developer, Maintenance
       Lead, etc.):
    Specification Name(s) and Version(s):
    Test Suite Name and Version:
    Test Name:
    Defense (argument for why test is valid):
    [Multiple challenges and corresponding responses may be listed
       here.]
    Implications of test invalidity (e.g., other affected tests and test
       framework code, creation or exposure of ambiguities in spec (due
       to unspecified requirements), invalidation of the reference
       implementation, creation of serious holes in test suite):
    Alternatives (e.g., are alternate test(s) appropriate?):
## 2.3 Reference Runtime for SOAP with Attachments API for Java 1.3 Designated Reference Implementation for compatibility testing of SOAP with Attachments API for Java 1.3 is as follows: Java SE 5 for Solaris OE/SPARC, and Win32 Sun Reference Implementation of SAAJ Version1.3. Sun Solaris/SPARC 2.8 and 2.9, Red Hat Linux 7.2, and Microsoft Windows XP/ 2000 ## 2.4 Specifications for SOAP with Attachments API for Java 1.3 The Specifications for Java SE 5 are found on the Java Partner Engineering web site. ## 2.5 Libraries for SOAP with Attachments API for Java 1.3 The following is a list of the packages comprising the required class libraries SAAJ 1.3:
    javax.xml.soap
For the latest list of packages, also see: http://java.sun.com/j2se/1.5/docs/api/index.html
| Previous Contents Next

Company Info Contact Terms of Use Privacy Copyright 1994-2006 Sun Microsystems, Inc.