API Definition Product |
A Product for which the only Java class files
contained in the product are those corresponding to the application
programming interfaces defined by the Specifications, and which is
intended only as a means for formally specifying the application
programming interfaces defined by the Specifications. |
Computational Resource |
A piece of hardware or software that may vary in quantity, existence, or
version, which may be required to exist in a minimum quantity and/or at
a specific or minimum revision level so as to satisfy the requirements
of the Test Suite.
Examples of computational resources that may vary in quantity are RAM
and file descriptors.
Examples of computational resources that may vary in existence (that is,
may or may not exist) are graphics cards and device drivers.
Examples of computational resources that may vary in version are
operating systems and device drivers.
|
Configuration Descriptor |
Any file whose format is well defined by a
specification and which contains configuration information for a set of
Java classes, archive, or other feature defined in the specification. |
Conformance Tests |
All tests in the Test Suite for an indicated
Technology Under Test, as released and distributed by the
Eclipse Foundation, excluding those tests on the
published Exclude List for the Technology Under Test. |
Container |
An implementation of the associated Libraries, as specified
in the Specifications, and a version of a Java Platform, Standard
Edition Runtime Product, as specified in the Specifications, or a later
version of a Java Platform, Standard Edition Runtime Product that also
meets these compatibility requirements. |
Documented |
Made technically accessible and made known to users,
typically by means such as marketing materials, product documentation,
usage messages, or developer support programs. |
Exclude List |
The most current list of tests, released and distributed by the
Eclipse Foundation, that are not required to be passed to certify
conformance. The Jakarta EE Specification Committee may add to the Exclude List for that
Test Suite as needed at any time, in which case the updated TCK version
supplants any previous Exclude Lists for that Test Suite. |
Libraries |
The class libraries, as specified through the Jakarta EE Specification Process
(JESP), for the Technology Under Test.
The Libraries for Jakarta RESTful Web Services are listed at the end of this chapter.
|
Location Resource |
A location of classes or native libraries that are components of the
test tools or tests, such that these classes or libraries may be
required to exist in a certain location in order to satisfy the
requirements of the test suite.
For example, classes may be required to exist in directories named in a
CLASSPATH variable, or native libraries may be required to exist in
directories named in a PATH variable.
|
Maintenance Lead |
The corresponding Jakarta EE Specification Project
is responsible for maintaining the Specification, and the TCK for the
Technology. The Specification Project Team will propose revisions and
updates to the Jakarta EE Specification Committee which will approve
and release new versions of the specification and TCK. |
Operating Mode |
Any Documented option of a Product that can be changed by a user in
order to modify the behavior of the Product.
For example, an Operating Mode can be binary (enable/disable
optimization), an enumeration (select from a list of protocols), or a
range (set the maximum number of active threads).
Note that an Operating Mode may be selected by a command line switch, an
environment variable, a GUI user interface element, a configuration or
control file, etc.
|
Product |
A vendor’s product in which the Technology Under Test is
implemented or incorporated, and that is subject to compatibility
testing. |
Product Configuration |
A specific setting or instantiation of an Operating Mode.
For example, a Product supporting an Operating Mode that permits user
selection of an external encryption package may have a Product
Configuration that links the Product to that encryption package.
|
Rebuildable Tests |
Tests that must be built using an
implementation-specific mechanism. This mechanism must produce
specification-defined artifacts. Rebuilding and running these tests
against a known compatible implementation verifies that the mechanism generates
compatible artifacts. |
Resource |
A Computational Resource, a Location Resource, or a Security
Resource. |
Rules |
These definitions and rules in this Compatibility Requirements
section of this User’s Guide. |
Runtime |
The Containers specified in the Specifications. |
Security Resource |
A security privilege or policy necessary for the proper execution of the
Test Suite.
For example, the user executing the Test Suite will need the privilege
to access the files and network resources necessary for use of the
Product.
|
Specifications |
The documents produced through the Jakarta EE Specification Process (JESP)
that define a particular Version of a Technology.
The Specifications for the Technology Under Test are referenced later in
this chapter.
|
Technology |
Specifications and one or more compatible implementations produced
through the Jakarta EE Specification Process (JESP). |
Technology Under Test |
Specifications and a compatible implementation
for Jakarta RESTful Web Services Version 4.0. |
Test Suite |
The requirements, tests, and testing tools distributed by
the Maintenance Lead as applicable to a given Version of the Technology. |
Version |
A release of the Technology, as produced through the
Jakarta EE Specification Process (JESP). |