<!-- Fragment document type declaration subset:
Arbortext, Inc., 1988-2006, v.4002
<!DOCTYPE SOLBOOK PUBLIC "-//Sun Microsystems//DTD SolBook 3.1//EN" [
<!ENTITY % TCKentities SYSTEM "TCKentities.ent">
%TCKentities;
]>
-->
<?Pub UDT _bookmark _target>
<?Pub CX solbook(>
<chapter id="GBFSN"><title>Procedure for &TechnologyFullName; Certification</title>
<highlights>
<para>This chapter describes the compatibility testing process and compatibility
requirements for &TechnologyFullName;. This chapter contains the following
sections:</para>
<itemizedlist>
<listitem><para><olink targetptr="GBFTE">Certification Overview</olink></para>
</listitem>
<listitem><para><olink targetptr="GBFRK">Compatibility Requirements</olink></para>
</listitem>
<listitem><para><olink targetptr="GBFTQ">Reference Runtime for &TechnologyFullName;</olink></para>
</listitem>
<listitem><para><olink targetptr="GBFTL">Specifications for &TechnologyFullName;</olink></para>
</listitem>
<listitem><para><olink targetptr="GBFTV">Libraries for &TechnologyFullName;</olink></para>
</listitem>
</itemizedlist>
</highlights>
<sect1 id="GBFTE"><?Pub Dtl><title>Certification Overview</title>
<para>The certification process for &TechnologyFullName; consists of the following
activities:</para>
<itemizedlist>
<listitem><para>Install the appropriate version of the Technology Compatibility
Kit (TCK) and execute it in accordance with the instructions in this User's
Guide.</para></listitem>
<listitem><para>Ensure that you meet the requirements outlined in <olink
type="custom-text" targetptr="GBFRK">Compatibility Requirements</olink>.</para>
</listitem>
<listitem><para>Certify to Java Licensee Engineering that you have finished
testing and that you meet all the compatibility requirements.</para></listitem>
</itemizedlist>
</sect1>
<sect1 id="GBFRK"><title>Compatibility Requirements</title>
<para>The compatibility requirements for &TechnologyFullName; consist of meeting
the requirements set forth by the rules and associated definitions contained
in this section.</para>&TCKdefinitions;
&TCKrules;
<sect2 id="GBFRX"><title>&TechnologyFullName; Test Appeals Process</title>
<para>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 &TechnologyFullName; requires one or more subcomponent TCKs,
the &TechnologyFullName; test appeals process will be consistent with the
existing subcomponent TCK test appeals processes. Sun, as &TechnologyFullName;,
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 &TCKFullName; support.</para>
<para>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 &TCKFullName;. 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:</para>
<itemizedlist>
<listitem><para>Test has bugs (i.e., program logic errors)</para></listitem>
<listitem><para>Specification item covered by the test is ambiguous</para>
</listitem>
<listitem><para>Test does not match the specification</para></listitem>
<listitem><para>Test assumes unreasonable hardware and/or software requirements</para>
</listitem>
<listitem><para>Test is biased to a particular implementation</para></listitem>
</itemizedlist>
<para>Challenges based upon issues unrelated to technical correctness as defined
by the specification will normally be rejected.</para>
<para>Test challenges must be made in writing to Java Licensee Engineering
and include all relevant information as described in the  <olink
type="custom-text" targetptr="GBFUA">Test Challenge Form</olink>. The process
used to determine the validity or invalidity of a test (or related group of
tests) is described in &ldquo;<olink type="custom-text" targetptr="GBFSF">&TCKFullName; Test
Appeals Steps</olink>.&rdquo;</para>
<para>All tests found to be invalid will either be placed on the Exclude List
for that version of the &TCKFullName; or have an alternate test made available.</para>
<itemizedlist><?Pub Caret>
<listitem><para>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 &TCKFullName; licensees
on the &TCKFullName; Web site.</para></listitem>
<listitem><para>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 &TCKFullName; Web site.</para></listitem>
</itemizedlist>
<note><para>Passing an alternative test is deemed equivalent to passing the
original test.</para></note>
<task id="GBFSF"><title>&TCKFullName; Test Appeals Steps</title>
<procedure>
<step><para>&TCKFullName; licensee writes a test challenge to Java Licensee
Engineering contesting the validity of one or a related set of &TechnologyFullName; tests.
</para><para>A detailed justification for why each test should be invalidated
must be included with the challenge as described by the  <olink
type="custom-text" targetptr="GBFUA">Test Challenge Form</olink>.</para></step>
<step><para>Java Licensee Engineering evaluates the challenge.</para><para>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 <olink type="custom-text"
targetptr="GBFUO">Test Challenge Response Form</olink>. 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.</para>
</step>
<step><para>The challenge and any supporting materials from test developers
is sent to the specification engineers for evaluation.</para><para>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.</para></step>
<step><para>The licensee is informed of the decision and proceeds accordingly.</para>
<para>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 &TCKFullName; (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).</para>
</step>
<step><para>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.</para></step>
</procedure>
</task>
<sect3 id="GBFUA"><title>Test Challenge Form</title>
<para>Provide the following information to Java Licensee Engineering:</para>
<programlisting>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):</programlisting>
</sect3>
<sect3 id="GBFUO"><title>Test Challenge Response Form</title>
<para>Provide the following information in response to a test challenge.</para>
<programlisting>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?):</programlisting>
</sect3>
</sect2>
</sect1>
<sect1 id="GBFTQ"><?Pub Dtl><title>Reference Runtime for &TechnologyFullName;</title>
<para>Designated Reference Implementation for compatibility testing of &TechnologyFullName; is
as follows:</para>
<itemizedlist>
<listitem><para>&J2SEversion; for Solaris OE/SPARC, and Win32</para></listitem>
<listitem><para>Sun Reference Implementation of &TechnologyShortName; Version&TechnologyVersion;.
</para></listitem>
<listitem>&RISupportedPlatforms;</listitem>
</itemizedlist>
</sect1>
<sect1 id="GBFTL"><?Pub Dtl><title>Specifications for &TechnologyFullName;</title>
<para>The Specifications for &J2SEversion; are found on the &JavaPartnerURL; web
site.</para></sect1>
<sect1 id="GBFTV"><?Pub Dtl><title>Libraries for &TechnologyFullName;</title>
<para>The following is a list of the packages comprising the required class
libraries &TechnologyShortName; &TechnologyVersion;:</para>&APIList;
<para>For the latest list of packages, also see:</para>
<para><ulink url="http://java.sun.com/j2se/1.5/docs/api/index.html" type="url">http://java.sun.com/j2se/1.5/docs/api/index.html
</ulink></para></sect1>
</chapter>
<?Pub *0000009821 0>
