<!-- Fragment document type declaration subset:
Arbortext, Inc., 1988-2008, v.4002
<!DOCTYPE SOLBOOK PUBLIC "-//Sun Microsystems//DTD SolBook 3.1//EN" [
<!ENTITY % TCKentities SYSTEM "TCKentities.ent">
%TCKentities;
]>
-->
<?Pub UDT _bookmark _target>
<?Pub EntList bull rArr sect>
<?Pub CX solbook(book(title()subtitle()bookinfo()chapter()>
<chapter id="GBFSN"><title>Procedure for &TechnologyFullName; Certification</title>
<highlights><?Pub Dtl>
<para>This chapter describes the compatibility testing process and compatibility
requirements for &TechnologyFullName; (&JSR;). 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 Java API for
RESTful Web Services 1.0</olink></para></listitem>
<listitem><para><olink targetptr="GBFTL">Specifications for Java API for RESTful
Web Services 1.0</olink></para></listitem>
<listitem><para><olink targetptr="GBFTV">Libraries for Java API for RESTful
Web Services 1.0</olink></para></listitem>
</itemizedlist>
</highlights>
<sect1 id="GBFTE"><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
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;
</sect1>
<sect1 id="GJKXM"><title>&TechnologyFullName; &TechnologyVersion; 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. Sun, as &TechnologyFullName; &TechnologyVersion; Maintenance Lead,
will authorize representatives from the &JavaLicenseeEngineeringShort; 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 &JavaLicenseeEngineeringShort; and
include all relevant information as described in step 1 in  <olink
type="custom-text" targetptr="GBFSF">&TCKFullName; Test Appeals Steps</olink>.
The process used to determine the validity or invalidity of a test (or related
group of tests) is also described in that section.</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>
<listitem><para>Tests that are placed on the Exclude List will be placed on
the Exclude List after the determination of test validity. The new Exclude
List will be made available to all &TCKFullName; licensees on the &JavaLicenseeEngineeringShort; 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="GJKXV"><title>&TCKFullName; Test Appeals Steps</title>
<procedure>
<step><para>&TCKFullName; licensee writes a test challenge to &JavaLicenseeEngineeringShort; contesting
the validity of one or a related set of &TechnologyFullName; &TechnologyVersion; tests.
</para><para>A challenge must be provided to &JavaLicenseeEngineeringShort; and
include the following information justifying why each test should be invalidated.
</para>
<programlisting>Date:
Licensee:
License Contact:
TCK name and version:
RI version:
Java SE version:
Exclude List version:
Specification version &amp; section:
Problem Description:
Tests Affected:
Output (inline/attach .jtr file and traces):</programlisting>
</step>
<step><para>&JavaLicenseeEngineeringShort; 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, &JavaLicenseeEngineeringShort; will check
with the responsible test developers to review the purpose and validity of
the test before writing a response. &JavaLicenseeEngineeringShort; 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), &JavaLicenseeEngineeringShort; will
send the previous response to the licensee.</para></step>
<step><para>In necessary, the challenge and any supporting materials from
test developers is sent to the assigned Java Licensee engineer or Specification
Lead for evaluation.</para><para>This step only happens if the test engineers
cannot come to a resolution. The issue may fall into a grey area and require
clarification from the Specification Lead. 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>
</sect1>
<sect1 id="GBFTQ"><title>Reference Runtime for &TechnologyFullName; &TechnologyVersion;</title>
<para>Designated Reference Implementation for compatibility testing of &TechnologyFullName; &TechnologyVersion; is
as follows:</para>
<itemizedlist>
<listitem><para>&J2SEversion; for Solaris x86/SPARC, and Win32</para></listitem>
<listitem><para>Sun Reference Implementation of &TechnologyShortName; Version &RIVersion;.
</para></listitem>
</itemizedlist>
</sect1>
<sect1 id="GBFTL"><title>Specifications for &TechnologyFullName; &TechnologyVersion;</title>
<para>The &TechnologyFullName; specification is available on the &JSR; Web
site at &SpecURL; or on the &JCPURL; site.</para></sect1>
<sect1 id="GBFTV"><title>Libraries for &TechnologyFullName; &TechnologyVersion;</title>
<para>The following is a list of the packages comprising the required class
<?Pub Caret>libraries &TechnologyShortName; &TechnologyVersion;:</para>&APIList;
<para>For the latest list of packages, also see:</para>
<itemizedlist>
<listitem><para><ulink url="http://jcp.org/en/jsr/detail?id=311" type="url"></ulink></para>
</listitem>
<listitem><para><ulink url="https://jsr311.dev.java.net/" type="url"></ulink></para>
</listitem>
</itemizedlist>
</sect1>
</chapter>
<?Pub *0000009060 0>
