diff --git a/user_guides/jakartaee/pom.xml b/user_guides/jakartaee/pom.xml index 86523b6d96..17f34a4a11 100644 --- a/user_guides/jakartaee/pom.xml +++ b/user_guides/jakartaee/pom.xml @@ -28,7 +28,7 @@ cts_javaee pom 9.0.0 - Eclipse Foundation Jakarta EE Platform, Enterprise Edition Compatibility Test Suite User's Guide, Release 9 + Eclipse Foundation Jakarta EE Platform, Enterprise Edition Test Compatibility Kit User's Guide, Release 9 UTF-8 diff --git a/user_guides/jakartaee/src/main/jbake/assets/_config.yml b/user_guides/jakartaee/src/main/jbake/assets/_config.yml index a272ae6fc7..b3d2f36589 100644 --- a/user_guides/jakartaee/src/main/jbake/assets/_config.yml +++ b/user_guides/jakartaee/src/main/jbake/assets/_config.yml @@ -1,7 +1,7 @@ remote_theme: jakartaee/jekyll-theme-jakarta-ee title: [cts_javaee_v8_0] -description: [Eclipse Jakarta EE Platform, Compatibility Test Suite User's Guide for Technology Implementers, Release 9] +description: [Eclipse Jakarta EE Platform, Test Compatibility Kit User's Guide for Technology Implementers, Release 9] # sidebar links url links: diff --git a/user_guides/jakartaee/src/main/jbake/content/TCKpreface.adoc b/user_guides/jakartaee/src/main/jbake/content/TCKpreface.adoc index 0695560da0..dea9c4e099 100644 --- a/user_guides/jakartaee/src/main/jbake/content/TCKpreface.adoc +++ b/user_guides/jakartaee/src/main/jbake/content/TCKpreface.adoc @@ -28,12 +28,13 @@ Please see the Title page for additional license information. ======================================================================== This book introduces the Test Compatibility Kit (TCK) for the Jakarta -Platform 9 full profile (Jakarta EE 9) and Jakarta Platform 9 Web Profile (Jakarta EE 9 Web Profile), and explains how to +Platform, Enterprise Edition 9 (Jakarta EE 9) and Jakarta Platform, Enterprise +Edition 9 Web Profile (Jakarta EE 9 Web Profile), and explains how to configure and run the test suite. It also provides information for troubleshooting problems you may encounter as you run the test suite. -The Jakarta Platform, Enterprise Edition 9 Compatibility Test Suite (Jakarta -EE 9 Platform TCK) is a portable, configurable automated test suite for verifying +The Jakarta Platform, Enterprise Edition 9 Test Compatibility Kit (Jakarta +EE 9 TCK) is a portable, configurable automated test suite for verifying the compatibility of an implementer's compliance with the Jakarta EE 9 Specification (hereafter referred to as the implementer's implementation, or VI). The Jakarta EE 9 Platform TCK uses the JavaTest harness version 5.0 to run the diff --git a/user_guides/jakartaee/src/main/jbake/content/building.adoc b/user_guides/jakartaee/src/main/jbake/content/building.adoc index febfdd5601..80d38d7a18 100644 --- a/user_guides/jakartaee/src/main/jbake/content/building.adoc +++ b/user_guides/jakartaee/src/main/jbake/content/building.adoc @@ -22,7 +22,7 @@ to use Ant with the following targets to rebuild, list, and run tests: * `build` * `ld`, `lld`, `lc`, `llc`, `pd`, `pc` -Implementers can only run the version of the tests provided with the TCK +Implementers can only run the version of the tests provided with the CTS for certification, except in the case of rebuildable tests. This chapter includes the following topics: @@ -44,7 +44,7 @@ the Solaris platform: 1. Set the following environment variables in your shell environment to use the build infrastructure that comes with the TCK: -* `TS_HOME` to the directory in which the Jakarta EE 9 TCK software is +* `TS_HOME` to the directory in which the Jakarta EE 9 Platform TCK software is installed. * `TS_HOME/bin` to your `PATH` in your command shell. * C Shell: + @@ -79,7 +79,7 @@ build infrastructure 10.2 Building the Tests ~~~~~~~~~~~~~~~~~~~~~~~ -To build the Jakarta EE 9 TCK tests using Ant, complete the following +To build the Jakarta EE 9 Platform TCK tests using Ant, complete the following steps: 1. To build a single test directory, type the following: + @@ -118,7 +118,7 @@ ant pc 10.3 Running the Tests ~~~~~~~~~~~~~~~~~~~~~~ -To run the Jakarta EE 9 TCK tests using Ant, use one of the following +To run the Jakarta EE 9 Platform TCK tests using Ant, use one of the following procedures. [[GFAOW]][[to-run-a-single-test-directory]] @@ -222,20 +222,20 @@ HelloHome.class 10.5 Debugging Service Tests ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -The Jakarta EE 9 TCK service tests test the compatibility of the Jakarta +The Jakarta EE 9 Platform TCK service tests test the compatibility of the Jakarta Platform, Enterprise Edition Service APIs: Jakarta Mail, JDBC, Jakarta Messaging, Jakarta Transactions, Jakarta XML Web Services, Jakarta Web Services Metadata, Jakarta Annotations. The test suite contains sets of -tests that the JavaTest harness, in conjunction with the Jakarta EE 9 TCK +tests that the JavaTest harness, in conjunction with the Jakarta EE 9 Platform TCK harness extensions, runs from different Jakarta Platform, Enterprise Edition containers (Jakarta Enterprise Beans, Jakarta Server Pages, Jakarta Servlet, and application client). The test suite wraps each of these tests inside generic -components, called vehicles. Each Jakarta EE 9 TCK service test has been +components, called vehicles. Each Jakarta EE 9 Platform TCK service test has been set up to run in a default set of vehicles. Each technology's specification determines this set. When run as part of the certification process, all service API tests must pass in their default vehicle set. Refer to the `/src/vehicle.properties` file to for a list the -default vehicle sets for the Jakarta EE 9 TCK service API tests. +default vehicle sets for the Jakarta EE 9 Platform TCK service API tests. To help you debug service API tests, the test suite provides a mechanism that allows for fine-grained control over which tests you can run in diff --git a/user_guides/jakartaee/src/main/jbake/content/config.adoc b/user_guides/jakartaee/src/main/jbake/content/config.adoc index 2a1f1be8b5..49a91886bd 100644 --- a/user_guides/jakartaee/src/main/jbake/content/config.adoc +++ b/user_guides/jakartaee/src/main/jbake/content/config.adoc @@ -98,11 +98,11 @@ directory. 3. Set up the Jakarta Platform, Enterprise Edition Compatible Implementation (CI) server. + See link:#GEWUI[Section 5.3.2, "Configuring the Jakarta EE 9 CI as the -VI,"] for a list of the modifications that must be made to run TCK +VI,"] for a list of the modifications that must be made to run CTS against the Jakarta EE 9 CI. 4. Set up the vendor's Jakarta EE 9 server implementation (VI). + See link:#GEWWA[Section 5.3.3, "Configuring Your Application Server as -the VI,"] for a list of the modifications that must be made to run TCK +the VI,"] for a list of the modifications that must be made to run CTS against the vendor's Jakarta EE 9 server. 5. Validate your configuration. + Run the sample tests provided. If the tests pass, your basic @@ -113,7 +113,7 @@ JavaTest to run the sample tests. See link:using.html#GBFWO[Chapter 7, "Executing Tests,"] for information about Starting JavaTest and running tests. -[[GEWTQ]][[configuring-a-java-ee-8-server]] +[[GEWTQ]][[configuring-a-jakarta-ee-9-server]] 5.3 Configuring a Jakarta EE 9 Server ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @@ -150,7 +150,7 @@ image:img/serverpath-ri.png["CI as Server Under Test"] Use the Jakarta EE 9 CI as the Jakarta EE 9 VI; you may want to do this as a sanity check to make sure you are comfortable with using the Jakarta EE 9 -Platform TCK against a known standard CI with certified sample applications +TCK against a known standard CI with certified sample applications before proceeding with tests against your Jakarta EE 9 VI. See link:#GEWUI[Section 5.3.2, "Configuring the Jakarta EE 9 CI as the VI,"] for instructions. @@ -172,7 +172,7 @@ VI running a database of your choice with JDBC 4.1-compliant drivers. The second server must be the Jakarta EE 9 CI using the bundled Java DB database. -In terms of the Jakarta EE 9 Platform TCK, all configuration settings are made +In terms of the Jakarta EE 9 Platform TCK, all TCK configuration settings are made in the `/bin/ts.jte` file. When configuring a Jakarta EE 9 server, the important thing is to make sure that the settings you use for your server match those in the `ts.jte` file. @@ -186,10 +186,10 @@ These configuration scenarios are described in the following sections. To configure the Jakarta EE 9 CI as the server under test (that is, to use the Jakarta EE 9 CI as the VI) follow the steps listed below. In this -scenario, the goal is simply to test the Jakarta EE 9 CI against the TCK +scenario, the goal is simply to test the Jakarta EE 9 CI against the CTS for the purposes of familiarizing yourself with TCK test procedures. You may also want to refer to the Quick Start guides included with the Jakarta -EE 9 Platform TCK for similar instructions. +EE 9 TCK for similar instructions. . Set server properties in your `/bin/ts.jte` file to suit your test environment. + @@ -214,7 +214,7 @@ The default setting for the CI porting implementation is `com.sun.ts.lib.implementation.sun.common.SunRIURL`. .. Set the database-related properties in the `/bin/ts.jte` file. + -link:database-config.html#GFKMW[Section D.3, "Database Properties in +link:database-config.html#GFKMW[Section C.3, "Database Properties in ts.jte,"] lists the names and descriptions for the database properties you need to set. .. Add the following JVM option to the `command.testExecuteAppClient` @@ -270,7 +270,7 @@ ant -f xml/init.xml init.derby ---- + If you are not using Derby as your backend database, refer to -link:database-config.html#GFAVUb[Appendix D, "Configuring Your Backend +link:database-config.html#GFAVUb[Appendix C, "Configuring Your Backend Database."] + + [NOTE] @@ -368,7 +368,7 @@ implementation class that is used for obtaining URLs. .. Set the database-related properties in the `/bin/ts.jte` file. + -link:database-config.html#GFKMW[Section D.3, "Database Properties in +link:database-config.html#GFKMW[Section C.3, "Database Properties in ts.jte,"] lists the names and descriptions for the database properties you need to set. @@ -413,10 +413,10 @@ The `/bin` directory contains the following `.dat` files: * `jws-url-props.dat` * `webservices12-url-props.dat` + -These files contain the webservice endpoint and WSDL URLs that the TCK +These files contain the webservice endpoint and WSDL URLs that the CTS tests use when running against the CI. In the porting package used by the TCK, the URLs are returned as is since this is the form that the CI -expects. You may need an alternate form of these URLs to run the TCK +expects. You may need an alternate form of these URLs to run the CTS tests in your environment. However, you MUST NOT modify the existing `.dat` files, but instead make any necessary changes in your own porting implementation class to transform the URLs appropriately for your @@ -455,7 +455,7 @@ ant -f /bin/xml/initdb.xml init.javadb ---- + -Refer to link:database-config.html#GFAVUb[Appendix D, "Configuring Your +Refer to link:database-config.html#GFAVUb[Appendix C, "Configuring Your Backend Database,"] for detailed database configuration and initialization instructions and a list of database-specific initialization targets. @@ -535,7 +535,7 @@ certificate that suits your environment. .. `cts_cert`: For importing the TCK client certificate into a `truststore` -.. `clientcert.jks`: Used by the Java SE 8 runtime to identify the TCK +.. `clientcert.jks`: Used by the Java SE 8 runtime to identify the CTS client's identity .. `clientcert.p12`: Contains TCK client certificate in `pkcs12` format @@ -649,7 +649,7 @@ back to their original values: . Continue on to link:using.html#GBFWO[Chapter 7, "Executing Tests"]. -[[GEXMH]][[configuring-a-jakarta-platform-enterprise-edition-ci-and-vi-for-interoprebuildable-tests]] +[[GEXPP]][[modifying-environment-settings-for-specific-technology-tests]] 5.4 Modifying Environment Settings for Specific Technology Tests ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @@ -684,7 +684,6 @@ This section includes the following topics: * link:#GEXOT[Jakarta Mail Test Setup] * link:#GEXPU[Jakarta XML Registry Test Setup] * link:#GJKPO[Jakarta RESTful Web Services Test Setup] -* link:#GEXQP[Deployment Test Setup] * link:#GEXOF[Jakarta Connector Test Setup] * link:#GEXPV[XA Test Setup] * link:#GKKOJ[Jakarta Enterprise Beans 4.0 Test Setup] @@ -722,7 +721,7 @@ porting.ts.tsHttpsURLConnection.class.1= ---- * The `harness.temp.directory` property specifies a temporary directory -that the harness creates and to which the CTS harness and tests write +that the harness creates and to which the TCK harness and tests write temporary files. The default setting should not need to be changed. * The `harness.log.port` property specifies the port that server @@ -747,10 +746,7 @@ to the Jakarta Platform, Enterprise Edition CI-specific classes. To run the interoperability tests, do not modify the `.2` set. These properties should always point to the Jakarta Platform, Enterprise Edition CI classes. Modify the `.1` set to point to implementations that work in your -specific Jakarta Platform, Enterprise Edition environment. See -link:#GEXMH[Configuring a Jakarta Platform, Enterprise Edition CI and VI -for Interop/Rebuildable Tests] for additional information about setting -these properties. +specific Jakarta Platform, Enterprise Edition environment. * The `-Dcts.tmp` option for the `testExecute` and `testExecuteAppClient` commands in the `ts.jte` file have been set. This @@ -767,10 +763,10 @@ following properties in `/bin/ts.jte`: * `pathsep` to semicolon (pathsep=`;`) -* `s1as.applicationRoot` to the drive on which you have installed Platform TCK +* `s1as.applicationRoot` to the drive on which you have installed CTS (for example, `s1as.applicationRoot=C:`) + When installing in the Windows environment, the Jakarta Platform, -Enterprise Edition CI, JDK, and Platform TCK should all be installed on the same +Enterprise Edition CI, JDK, and TCK should all be installed on the same drive. If you must install these components on different drives, also change the `ri.applicationRoot` property in addition to the `pathsep` and `s1as.applicationRoot` properties; for example: + @@ -783,7 +779,7 @@ ri.applicationRoot=C: [NOTE] ======================================================================= -When configuring the CI and Platform TCK for the Windows environment, never +When configuring the CI and TCK for the Windows environment, never specify drive letters in any path properties in `ts.jte`. ======================================================================= @@ -930,7 +926,7 @@ properties. The SSL related tests under `/ts/javaeetck/src/com/sun/ts/tests/websocket/platform/jakarta/websocket/server/handshakerequest/authenticatedssl/` -use self signed certificate bundled with the Platform TCK bundle. These +use self signed certificate bundled with the TCK bundle. These certificates are generated with localhost as the hostname and would work only when orb.host value is set to localhost in ts.jte. If the server's hostname is used instead of the localhost, the tests in this suite might @@ -1109,7 +1105,7 @@ All resource and application class files are already compiled. The Vendor needs to package these files. Jakarta EE 9 Platform TCK makes this task easier by including template WAR files that contain all of the necessary files except for the VI-specific servlet adaptor class. The Jakarta EE 9 -Platform TCK also provides a tool to help with the repackaging task. +TCK also provides a tool to help with the repackaging task. Each test that has a Jakarta RESTful Web Services resource class to publish comes with a template deployment descriptor file. For example, the file @@ -1366,7 +1362,7 @@ copied. 5.4.9.4 Required Porting Package +++++++++++++++++++++++++++++++++ -The Jakarta EE 9 Platform TCK treats the `whitebox.jar` dependency as an +The Jakarta EE 9 Platform TCK test suite treats the `whitebox.jar` dependency as an Installed Library dependency instead of bundling the dependency (or dependencies) with every RAR file. Each RAR file now contains a reference to the `whitebox.jar` file through its Manifest files @@ -1703,7 +1699,7 @@ CI as the VI]. Your Jakarta Platform, Enterprise Edition implementation should map the following instance variables to a backend datastore. These are needed to -run the Platform TCK entity bean container-managed persistence (cmp1.1) tests. +run the TCK entity bean container-managed persistence (cmp1.1) tests. The Jakarta Platform, Enterprise Edition CI creates the table used by container-managed persistence by appending `"Table"` to the bean name. @@ -1779,15 +1775,15 @@ The Jakarta Persistence Pluggability tests under the `src/com/sun/ts/tests/jpa/ee/pluggability` directory ensure that a third-party persistence provider is pluggable, in nature. -After Java EE 7 CTS, the pluggability tests were rewritten to use a +After Java EE 7 TCK, the pluggability tests were rewritten to use a stubbed-out legacy JPA 2.1 implementation, which is located in the `src/com/sun/ts/jpa/common/pluggibility/altprovider` directory. -In Java EE 7 CTS, the Persistence API pluggability tests required +In Java EE 7 TCK, the Persistence API pluggability tests required special setup to run. This is no longer the case, since Jakarta EE 9 Platform TCK now enables the pluggability tests to be executed automatically along with all the other Persistence tests. The Jakarta Persistence tests have a new -directory structure. In Java EE 7 CTS, the tests were in the +directory structure. In Java EE 7 TCK, the tests were in the `src/com/sun/ts/tests/ejb30/persistence` directory. The Jakarta EE 9 tests are now in the `src/com/sun/ts/tests/jpa` directory. @@ -1798,7 +1794,7 @@ the `src/com/sun/ts/tests/jpa` directory. Jakarta Persistence supports the use of a second-level cache by the persistence provider. The `ts.jte` file provides a property that -controls the Platform TCK test suite's use of the second-level cache. +controls the TCK test suite's use of the second-level cache. The `persistence.second.level.caching.supported` property is used to determine if the persistence provider supports the use of a second-level @@ -1874,7 +1870,7 @@ supports the use of SEQUENCE. If it does not, this property should be set to false so the test is not run. The default value is true. If the database under test is not one of the databases defined and -supported by Platform TCK, the user will need to create an entry similar to the +supported by TCK, the user will need to create an entry similar to the one listed in link:#GEXOO[Example 5-1]. [[GEXOO]] @@ -1892,7 +1888,7 @@ INSERT into SEQUENCE(SEQ_NAME, SEQ_COUNT) values ('SEQ_GEN', 0) ; You should add your own table to your chosen database DDL file provided prior to running these tests. The Data Model used to test the Jakarta Persistence Query Language can be found in -link:ejbql-schema.html#GFAVUc[Appendix E, "EJBQL Schema."] +link:ejbql-schema.html#GFAVUc[Appendix D, "EJBQL Schema."] The `persistence.xml` file, which defines a persistence unit, contains the `unitName` `CTS-EM` for Jakarta Transactions entity managers. This corresponds to @@ -1905,7 +1901,7 @@ entity managers, which correspond to a `non-jta-data-source` 5.4.15 Jakarta Messaging Test Setup ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -This section explains how to set up and configure the Jakarta EE 9 Platform TCK +This section explains how to set up and configure the Jakarta EE 9 Platform TCK test suite before running the Jakarta Messaging tests. @@ -1913,7 +1909,7 @@ suite before running the Jakarta Messaging tests. ======================================================================= The client-specified values for `JMSDeliveryMode`, `JMSExpiration`, and -`JMSPriority` must not be overridden when running the Platform TCK Jakarta Messaging tests. +`JMSPriority` must not be overridden when running the TCK Jakarta Messaging tests. ======================================================================= @@ -2280,17 +2276,17 @@ been times when it has caused problems. The recommended course of action is to deploy the test archive for the directory under test. Once done, remove that archive and move onto another directory. -The Jakarta Authorization-CTS provider acts as a delegating security provider sitting +The Jakarta Authorization-TCK provider acts as a delegating security provider sitting between the appserver and vendor provider. The Jakarta Platform, Enterprise Edition appserver comes with a default security provider that is defined by two system properties; for the purposes of this discussion, these are referred to as `A=DefaultProviderFactory` and `B=DefaultPolicyModule`. -CTS moves the values from A and B to two new variables: +TCK moves the values from A and B to two new variables: `C=DefaultProviderFactory` and `D=DefaultPolicyModule`, replacing the -CTS provider classes to the variables `A` and `B` (`A=TSProviderFactory` +TCK provider classes to the variables `A` and `B` (`A=TSProviderFactory` and `B=TSPolicyModule`). This modification allows the server to call the -CTS provider for all its functions, and the CTS provider in turn uses +TCK provider for all its functions, and the TCK provider in turn uses these new variables to invoke the real provider. The property names `A`, `B`, `C`, and `D` are used for convenience here. @@ -2378,7 +2374,7 @@ Jakarta Platform, Enterprise Edition CI webservice runtime DTDs contain two new optional elements for publishing and lookup of final WSDLs for a deployed webservice endpoint. These new tags are `` and ``, and are used by the CTS -to automate all CTS webservices tests, regardless of the host or port +to automate all TCK webservices tests, regardless of the host or port used to run the tests. These WSDL tags are also used when performing file URL publishing, as @@ -2399,7 +2395,7 @@ endpoint. As stated above, the final WSDL can be published to a file URL or http URL, although the tag is really only necessary for file URL publishing, and is ignored if http URL publishing is specified (http is the default publishing used by the Jakarta Platform, Enterprise Edition -CI). This tag is included in all CTS tests for consistency and to aid as +CI). This tag is included in all TCK tests for consistency and to aid as a mechanism in automation. By default, the Jakarta Platform, Enterprise Edition CI publishes the final @@ -2418,7 +2414,7 @@ specified in the `` tag. 5.4.19.1 WSDL ts.jte Properties +++++++++++++++++++++++++++++++ -For file URL publishing, the CTS defines two properties in the `ts.jte` +For file URL publishing, the TCK defines two properties in the `ts.jte` file, named `wsdlRepository1` and `wsdlRepository2`, which specify the file system directory location to use for publishing final WSDLs that use file URL publishing. @@ -2427,7 +2423,7 @@ The `wsdlRepository1` is used for the Vendor Jakarta Platform, Enterprise Edition Implementation. The `wsdlRepository2` is used for the CI Jakarta Platform, Enterprise Edition Implementation, and is only used for CTS webservices interoperability testing. These directories get created by -the CTS harness at runtime. The default settings in the `ts.jte` file +the TCK harness at runtime. The default settings in the `ts.jte` file will create these directories under: [source,oac_no_warn] @@ -2452,7 +2448,7 @@ file:wsdlRepository1/Simple1File/Simple1FileSvc.wsdl ---- -In this case, the CTS harness substitutes `wsdlRepository1` with the +In this case, the TCK harness substitutes `wsdlRepository1` with the setting in the `/bin/ts.jte` file. For `http` URL publishing, the tag settings might be: @@ -2471,7 +2467,7 @@ http://webServerHost.1:webServerPort.1/Simple1Http/ws4ee?WSDL ---- -In this case, the CTS harness substitutes the +In this case, the TCK harness substitutes the webServerHost.1:webServerPort.1 with the settings in the `/bin/ts.jte` file. @@ -2479,7 +2475,7 @@ webServerHost.1:webServerPort.1 with the settings in the [NOTE] ======================================================================= -In the case of interop webservices tests, the CTS harness substitutes +In the case of interop webservices tests, the TCK harness substitutes the `webServerHost.2:webServerPort.2` with the settings in the `ts.jte` file. This host and port defines the CI Jakarta Platform, Enterprise Edition implementation used as the interop test machine. See @@ -2669,7 +2665,7 @@ a file URL; for example: 5.4.19.3 Webservice Client WSDL Elements ++++++++++++++++++++++++++++++++++++++++ -In the CTS for file publishing, the directory in which to publish the +In the TCK for file publishing, the directory in which to publish the file WSDL is specified in the `` tag for the webservice, and the full path of the WSDL file is specified in the `` tag in the client; for example: @@ -2696,7 +2692,7 @@ META-INF/wsdl/a/b/Main.wsdl META-INF/wsdl/Relative.wsdl ---- -The `wsdl-publish-location` tells the CTS where to locate the topmost +The `wsdl-publish-location` tells the TCK where to locate the topmost part of the WSDL content hierarchy. So, given a `wsdl-publish-location` of `/home/foo/wsdlpublishdir`, this location would look like: @@ -2738,35 +2734,12 @@ Interface is mapped. Only required for each `port-component-ref` in the ---- -[[GEYMN]][[setting-stub-properties]] +[[GEYOG]][[overriding-wsdl]] -5.4.19.3.2 Setting Stub Properties +===== 5.4.19.3.2 Overriding WSDL -* Setting Logging property (Implementation-specific): + -Name: `com.sun.enterprise.webservice.client.transport.log` + -Value: a `file` URL + -This is useful for debugging. When set, all soap/http requests and -responses made through the associated stub will be logged to a file. -+ [source,oac_no_warn] ---- -appclient.jar - - service/GoogleSearch - - google.GoogleSearchPort - - - urn:GoogleSearch - GoogleSearchPort - - - com.sun.enterprise.webservice.client.transport.log - file:/tmp/jaxrpc.log - - - ----- element : wsdl-override ---- @@ -2778,7 +2751,7 @@ cases, it must point to a valid URL of a full WSDL document. Some examples are shown below. * To use the final WSDL generated upon deployment of the EJB endpoint -shown above: +shown above: + [source,oac_no_warn] ---- @@ -2790,7 +2763,7 @@ shown above: ---- + * An alternate way to do the same thing by means of a file URL that -matches a webservice's `wsdl-publish-location` could be: +matches a webservice's `wsdl-publish-location` could be: + [source,oac_no_warn] ---- @@ -2814,7 +2787,7 @@ Complete the following steps before you run the Jakarta Security API tests: ======================================================================= An LDAP server is required in Jakarta Security API testing. You could either use -an already existing external LDAP server or use CTS script to install an +an already existing external LDAP server or use TCK script to install an internal LDAP server. ======================================================================= @@ -2852,7 +2825,7 @@ Parts of ts.jte: ======================================================================= . Ensure the port of LDAP server is 11389. -. Update ldap.install.server property as false since CTS script need +. Update ldap.install.server property as false since TCK script need not install LDAP server. . Import ldap.ldif file into Ldap server. You can get ldap.ldif from `/install/jakartaee/bin/ldap.ldif`. @@ -2953,8 +2926,7 @@ Tested version: 2.0_se8 Check mode: src [throws normalized] Constant checking: on -Missing Fields --------------- +Missing Fields : jakarta.servlet.jsp.jstl.core.Config: field public final static java.lang.String jakarta.servlet.jsp.jstl.core.Config.FMT_FALLBACK_LOCALE = "jakarta.servlet.jsp.jstl.fmt.fallbackLocale" jakarta.servlet.jsp.jstl.core.Config: field public final static java.lang.String jakarta.servlet.jsp.jstl.core.Config.FMT_LOCALE = "jakarta.servlet.jsp.jstl.fmt.locale" @@ -2963,8 +2935,7 @@ jakarta.servlet.jsp.jstl.core.Config: field public final static java.lang.Stri jakarta.servlet.jsp.jstl.core.Config: field public final static java.lang.String jakarta.servlet.jsp.jstl.core.Config.SQL_DATA_SOURCE = "jakarta.servlet.jsp.jstl.sql.dataSource" jakarta.servlet.jsp.jstl.core.Config: field public final static java.lang.String jakarta.servlet.jsp.jstl.core.Config.SQL_MAX_ROWS = "jakarta.servlet.jsp.jstl.sql.maxRows" -Added Fields ------------- +Added Fields : jakarta.servlet.jsp.jstl.core.Config: field public final static java.lang.String jakarta.servlet.jsp.jstl.core.Config.FMT_FALLBACK_LOCALE = "javax.servlet.jsp.jstl.fmt.fallbackLocale" jakarta.servlet.jsp.jstl.core.Config: field public final static java.lang.String jakarta.servlet.jsp.jstl.core.Config.FMT_LOCALE = "javax.servlet.jsp.jstl.fmt.locale" @@ -2992,16 +2963,14 @@ Tested version: 4.0_se8 Check mode: src [throws normalized] Constant checking: on -Missing Methods ---------------- +Missing Methods : jakarta.el.ELContext: method public java.lang.Object jakarta.el.ELContext.getContext(java.lang.Class) jakarta.el.ELContext: method public void jakarta.el.ELContext.putContext(java.lang.Class,java.lang.Object) jakarta.el.StandardELContext: method public java.lang.Object jakarta.el.StandardELContext.getContext(java.lang.Class) jakarta.el.StandardELContext: method public void jakarta.el.StandardELContext.putContext(java.lang.Class,java.lang.Object) -Added Methods -------------- +Added Methods : jakarta.el.ELContext: method public java.lang.Object jakarta.el.ELContext.getContext(java.lang.Class) jakarta.el.ELContext: method public void jakarta.el.ELContext.putContext(java.lang.Class,java.lang.Object) @@ -3079,7 +3048,7 @@ Edition server. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ You can use the JavaTest harness GUI to modify general test settings and -to quickly get started with the default Platform TCK test environment. After +to quickly get started with the default TCK test environment. After familiarizing yourself with these basic configuration settings, you will probably want to continue with the instructions in link:#GEXPP[Modifying Environment Settings for Specific Technology Tests]. @@ -3161,7 +3130,7 @@ directory. + If you already have a working directory you want to use, click *File*, then click *Open Work Directory* instead. + At this point, the JavaTest harness is preconfigured to run the basic -CTS tests. +TCK tests. . If you want to run the test suite at this time using your current configuration settings, select *Run Tests* from the main menu, then select diff --git a/user_guides/jakartaee/src/main/jbake/content/contextrootmappingrules.adoc b/user_guides/jakartaee/src/main/jbake/content/contextrootmappingrules.adoc index fc505b3a20..fc06efa517 100644 --- a/user_guides/jakartaee/src/main/jbake/content/contextrootmappingrules.adoc +++ b/user_guides/jakartaee/src/main/jbake/content/contextrootmappingrules.adoc @@ -7,9 +7,9 @@ prev=ejbql-schema.html Context Root Mapping Rules for Web Services Tests ================================================= -[[GJJWH]][[f-context-root-mapping-rules-for-web-services-tests]] +[[GJJWH]][[e-context-root-mapping-rules-for-web-services-tests]] -F Context Root Mapping Rules for Web Services Tests +E Context Root Mapping Rules for Web Services Tests --------------------------------------------------- The context root mapping rules that are described in this appendix apply @@ -21,9 +21,9 @@ This appendix covers the following topics: * link:#GJJWR[Servlet-Based Web Service Endpoint Context Root Mapping] * link:#GJJWG[Jakarta Enterprise Bean-Based Web Service Endpoint Context Root Mapping] -[[GJJWR]][[f.1-servlet-based-web-service-endpoint-context-root-mapping]] +[[GJJWR]][[e.1-servlet-based-web-service-endpoint-context-root-mapping]] -F.1 Servlet-Based Web Service Endpoint Context Root Mapping +E.1 Servlet-Based Web Service Endpoint Context Root Mapping ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This section describes the context root mapping for servlet-based web @@ -83,9 +83,9 @@ The directory listing is as follows: For Web archives, the context root mapping becomes the base name of the Web archive file minus the extension. -[[GJJWG]][[f.2-jakarta-enterprise-bean-based-web-service-endpoint-context-root-mapping]] +[[GJJWG]][[e.2-jakarta-enterprise-bean-based-web-service-endpoint-context-root-mapping]] -F.2 Jakarta Enterprise Bean-Based Web Service Endpoint Context Root Mapping +E.2 Jakarta Enterprise Bean-Based Web Service Endpoint Context Root Mapping ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This section describes the context root mapping for Jakarta Enterprise Bean-based web diff --git a/user_guides/jakartaee/src/main/jbake/content/database-config.adoc b/user_guides/jakartaee/src/main/jbake/content/database-config.adoc index 2949e05b8f..c757cff709 100644 --- a/user_guides/jakartaee/src/main/jbake/content/database-config.adoc +++ b/user_guides/jakartaee/src/main/jbake/content/database-config.adoc @@ -7,14 +7,14 @@ prev=jaspic-files.html Configuring Your Backend Database ================================= -[[GFAVUb]][[d-configuring-your-backend-database]] +[[GFAVUb]][[c-configuring-your-backend-database]] -D Configuring Your Backend Database +C Configuring Your Backend Database ----------------------------------- This appendix explains how to configure a backend database to use with a Jakarta Platform, Enterprise Edition server being tested against the Jakarta -EE 9 Platform TCK. +EE 9 TCK. The topics included in this appendix are as follows: @@ -24,13 +24,13 @@ The topics included in this appendix are as follows: * link:#GFKOC[Database DDL and DML Files] * link:#GFKND[CMP Table Creation] -[[GFKNA]][[d.1-overview]] +[[GFKNA]][[c.1-overview]] -D.1 Overview +C.1 Overview ~~~~~~~~~~~~ All Jakarta Platform, Enterprise Edition servers tested against the Jakarta EE -9 Platform TCK must be configured with a database and JDBC 4.1-compliant drivers. +9 TCK must be configured with a database and JDBC 4.1-compliant drivers. Note that the Jakarta Platform, Enterprise Edition CI, Eclipse GlassFish 6.0 includes the Apache Derby database. @@ -50,8 +50,8 @@ required by the TCK. The database configuration process comprises four general steps: 1. Set database-related properties in the `/bin/ts.jte` file. -2. Configure your Jakarta Platform server -implementation for your database and for Platform TCK. +2. Configure your Jakarta Platform, Enterprise Edition server +implementation for your database and for TCK. 3. Start your database. 4. Run the `init.` Ant target to initialize your database for TCK. @@ -62,9 +62,9 @@ link:config.html#GEWTQ[Configuring a Jakarta EE 9 Server]. The final step, initializing your database for TCK by running `init.<`database> target, is explained more in the next section. -[[GFKNR]][[d.2-the-init.database-ant-target]] +[[GFKNR]][[c.2-the-init.database-ant-target]] -D.2 The init. Ant Target +C.2 The init. Ant Target ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Before your Jakarta Platform, Enterprise Edition server database can be @@ -99,9 +99,9 @@ backend for a specific database; for example, OracleInet/Oracle Inet driver; OracleDD/Oracle DataDirect driver. These targets are configured in the `/xml/initdb.xml` file. -[[GFKMW]][[d.3-database-properties-in-ts.jte]] +[[GFKMW]][[c.3-database-properties-in-ts.jte]] -D.3 Database Properties in ts.jte +C.3 Database Properties in ts.jte ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Listed below are the names and descriptions for the database properties @@ -198,9 +198,9 @@ Apache Derby. |======================================================================= -[[GFKOC]][[d.4-database-ddl-and-dml-files]] +[[GFKOC]][[c.4-database-ddl-and-dml-files]] -D.4 Database DDL and DML Files +C.4 Database DDL and DML Files ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For each supported database type, the Jakarta EE 9 Platform TCK includes a set of @@ -266,9 +266,9 @@ After updating `initdb.xml`, you invoke the new target with: ant -f /bin/xml/initdb.xml init.databasename ---- -[[GFKND]][[d.5-cmp-table-creation]] +[[GFKND]][[c.5-cmp-table-creation]] -D.5 CMP Table Creation +C.5 CMP Table Creation ~~~~~~~~~~~~~~~~~~~~~~ If the application server under test does not provide an option to diff --git a/user_guides/jakartaee/src/main/jbake/content/ejbql-schema.adoc b/user_guides/jakartaee/src/main/jbake/content/ejbql-schema.adoc index c12e2d74b5..f9c677c811 100644 --- a/user_guides/jakartaee/src/main/jbake/content/ejbql-schema.adoc +++ b/user_guides/jakartaee/src/main/jbake/content/ejbql-schema.adoc @@ -7,9 +7,9 @@ prev=database-config.html EJBQL Schema ============ -[[GFAVUc]][[e-ejbql-schema]] +[[GFAVUc]][[d-ejbql-schema]] -E EJBQL Schema +D EJBQL Schema -------------- The Jakarta Enterprise Beans, EJB-QL tests perform queries against a CMP 2.0 abstract persistence @@ -25,9 +25,9 @@ This appendix includes information about the following topics: * link:#GFKSI[Persistence Schema Relationships] * link:#GFKQT[SQL Statements for CMP 1.1 Finders] -[[GFKSI]][[e.1-persistence-schema-relationships]] +[[GFKSI]][[d.1-persistence-schema-relationships]] -E.1 Persistence Schema Relationships +D.1 Persistence Schema Relationships ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The figure, link:#GFKUU[Figure E-1], below, contains detailed @@ -186,9 +186,9 @@ CustomerLocal customer;(cmr) |================================ -[[GFKQT]][[e.2-sql-statements-for-cmp-1.1-finders]] +[[GFKQT]][[d.2-sql-statements-for-cmp-1.1-finders]] -E.2 SQL Statements for CMP 1.1 Finders +D.2 SQL Statements for CMP 1.1 Finders ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Listed below are the SQL statements used for CMP 1.1 finders in: @@ -198,9 +198,9 @@ Listed below are the SQL statements used for CMP 1.1 finders in: * `ejb/ee/bb/entity/cmp/complexpktest` * `ejb/ee/tx/txECMPbean` -[[GFKSD]][[e.2.1-ejbeebbentitycmpclientviewtest-interopejbentitycmpclientviewtest]] +[[GFKSD]][[d.2.1-ejbeebbentitycmpclientviewtest-interopejbentitycmpclientviewtest]] -E.2.1 ejb/ee/bb/entity/cmp/clientviewtest, interop/ejb/entity/cmp/clientviewtest +D.2.1 ejb/ee/bb/entity/cmp/clientviewtest, interop/ejb/entity/cmp/clientviewtest ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [source,oac_no_warn] @@ -219,9 +219,9 @@ E.2.1 ejb/ee/bb/entity/cmp/clientviewtest, interop/ejb/entity/cmp/clientviewtest SELECT "KEY_ID" FROM "TestBeanEJBTable" WHERE "BRAND_NAME" = ?1 ---- -[[GFKQU]][[e.2.2-ejbeebbentitycmpcomplexpktest]] +[[GFKQU]][[d.2.2-ejbeebbentitycmpcomplexpktest]] -E.2.2 ejb/ee/bb/entity/cmp/complexpktest +D.2.2 ejb/ee/bb/entity/cmp/complexpktest ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [source,oac_no_warn] @@ -234,9 +234,9 @@ E.2.2 ejb/ee/bb/entity/cmp/complexpktest SELECT "BRAND_NAME", "ID" FROM "TestBeanEJBTable" WHERE "BRAND_NAME" = ?1 ---- -[[GFKSB]][[e.2.3-ejbeetxtxecmpbean]] +[[GFKSB]][[d.2.3-ejbeetxtxecmpbean]] -E.2.3 ejb/ee/tx/txECMPbean +D.2.3 ejb/ee/tx/txECMPbean ^^^^^^^^^^^^^^^^^^^^^^^^^^ [source,oac_no_warn] diff --git a/user_guides/jakartaee/src/main/jbake/content/install.adoc b/user_guides/jakartaee/src/main/jbake/content/install.adoc index 4fabd9e0b1..7af658361c 100644 --- a/user_guides/jakartaee/src/main/jbake/content/install.adoc +++ b/user_guides/jakartaee/src/main/jbake/content/install.adoc @@ -14,7 +14,7 @@ Installation This chapter explains how to install the Jakarta EE 9 Platform TCK software and perform a sample test run to verify your installation and familiarize -yourself with the Platform TCK. Installation instructions are provided for Eclipse +yourself with the TCK. Installation instructions are provided for Eclipse GlassFish 6.0, a Compatible Implementation (CI) of Jakarta EE. If you are using another compatible implementation, refer to instructions provided with that implementation. @@ -59,10 +59,10 @@ EE 9 CI. /bin/asadmin start-domain ---- -[[GEVHP]][[installing-the-jakarta-ee-9-platform-TCK]] +[[GEVHP]][[installing-the-jakarta-ee-9-platform-tck]] 4.2 Installing the Jakarta EE 9 Platform TCK -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Complete the following procedure to install the Jakarta EE 9 Platform TCK on a system running the Solaris, Linux, or Windows operating system. @@ -82,18 +82,18 @@ more information. ======================================================================= -. Copy or download the Platform TCK 9 software. +. Copy or download the TCK 9 software. . Change to the directory in which you want to install the Jakarta EE 9 -CTS software and use the `unzip` command to extract the bundle: +TCK software and use the `unzip` command to extract the bundle: + [source,oac_no_warn] ---- cd install_directory -unzip jakartaee.zip +unzip jakartaeetck-nnn.zip ---- + This creates the `jakartaeetck` directory. The -install_directory`/javaeetck` directory will be `TS_HOME`. +install_directory`/jakartaeetck` directory will be `TS_HOME`. . Set the `TS_HOME` environment variable to point to the `javaeetck` directory. @@ -106,8 +106,8 @@ and configure the Jakarta EE 9 Platform TCK test suite. 4.3 Verifying Your Installation (Optional) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -This procedure is optional. After installing the Jakarta EE 9 CI and Java -EE 9 Platform TCK, you may want to verify your installation by running the TCK +This procedure is optional. After installing the Jakarta EE 9 CI and Jakarta +EE 9 TCK, you may want to verify your installation by running the TCK samples against the Jakarta EE 9 CI. See link:config.html#GBFVV[Chapter 5, "Setup and Configuration,"] for complete configuration instructions. diff --git a/user_guides/jakartaee/src/main/jbake/content/intro.adoc b/user_guides/jakartaee/src/main/jbake/content/intro.adoc index dcd4c78a6d..87a8c1b40b 100644 --- a/user_guides/jakartaee/src/main/jbake/content/intro.adoc +++ b/user_guides/jakartaee/src/main/jbake/content/intro.adoc @@ -13,7 +13,7 @@ Introduction -------------- This document provides instructions for installing, configuring, and -running the Jakarta Platform, Enterprise Edition 9 Compatibility Test Suite +running the Jakarta Platform, Enterprise Edition 9 Test Compatibility Kit (Jakarta EE 9 Platform TCK). This chapter includes the following topics: @@ -88,15 +88,15 @@ Profile. A Jakarta EE 9 Platform TCK is a set of tools and tests used to verify that a Implementer's implementation of Jakarta EE 9 technology conforms to the -applicable specification. All tests in the CTS are based on the written -specifications for the Jakarta Platform. The CTS tests compatibility of a +applicable specification. All tests in the TCK are based on the written +specifications for the Jakarta Platform. The TCK tests compatibility of a Implementer's implementation of a technology to the applicable specification of the technology. Compatibility testing is a means of ensuring correctness, completeness, and consistency across all implementations developed by technology Implementers. The set of tests included with the Jakarta EE 9 Platform TCK is called the test -suite. All tests in the CTS test suite are self-checking, but some tests +suite. All tests in the TCK test suite are self-checking, but some tests may require tester interaction. Most tests return either a Pass or Fail status. For a given platform to be certified, all of the required tests must pass. The definition of required tests may change from platform to @@ -108,7 +108,7 @@ List for the Jakarta EE 9 Platform TCK. The definition of required tests will ch over time. See link:#GEUYQ[Section 1.2.5, "Exclude Lists,"] for more information. -[[GBFPB]][[jakarta-specification-community-process-program-and-compatibility-testing]] +[[GBFPB]][[jakarta-community-community-process-program-and-compatibility-testing]] 1.1.4 Jakarta Specification Community Process Program and Compatibility Testing ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ @@ -131,7 +131,7 @@ Specification Process community page (https://jakarta.ee/specifications). [[GEUYK]][[about-jakarta-ee-9-platform-tck]] 1.2 About Jakarta EE 9 Platform TCK -~~~~~~~~~~~~~~~~~~~~~~~~~~ +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Jakarta EE 9 Platform TCK is a portable, configurable, automated test suite for verifying the compliance of a Implementer's implementation of the Jakarta EE 9 @@ -145,7 +145,7 @@ test suite, see [[sthref4]][[jakarta-ee-9-technologies-tested-with-jakarta-ee-9-platform-tck]] 1.2.1 Jakarta EE 9 Technologies Tested with Jakarta EE 9 Platform TCK -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The Jakarta EE 9 Platform TCK test suite includes compatibility tests for the following required and optional Jakarta EE 9 technologies: @@ -187,12 +187,10 @@ following required and optional Jakarta EE 9 technologies: * Jakarta XML Binding 3.0 (optional) -======================================================================= - [[BHCGFHDI]][[jakarta-ee-9-web-profile-technologies-tested-with-jakarta-ee-9-platform-tck]] 1.2.2 Jakarta EE 9 Web Profile Technologies Tested With Jakarta EE 9 Platform TCK -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The Jakarta EE 9 Platform TCK test suite can also be used to test compatibility for the following required Jakarta EE 9 Web Profile technologies: @@ -306,8 +304,8 @@ To run tests using the JavaTest harness, you specify which tests in the test suite to run, how to run them, and where to put the results as described in link:using.html#GBFWO[Chapter 7, "Executing Tests."] -The tests that make up the CTS are precompiled and indexed within the -CTS test directory structure. When a test run is started, the JavaTest +The tests that make up the TCK are precompiled and indexed within the +TCK test directory structure. When a test run is started, the JavaTest harness scans through the set of tests that are located under the directories that have been selected. While scanning, the JavaTest harness selects the appropriate tests according to any matches with the @@ -320,13 +318,13 @@ filters you are using and queues them up for execution. The Jakarta EE 9 Platform TCK includes an Exclude List contained in a `.jtx` file. This is a list of test file URLs that identify tests which do not have -to be run for the specific version of the CTS being used. Whenever tests +to be run for the specific version of the TCK being used. Whenever tests are run, the JavaTest harness automatically excludes any test on the Exclude List from being executed. A implementor is not required to pass or run any test on the Exclude List. The Exclude List file, `/bin/ts.jtx`, is included in the Jakarta -EE 9 CTS. +EE 9 TCK. [NOTE] @@ -384,7 +382,7 @@ flexible, cross-platform compatible, and centered around XML-based configuration files. Ant is invoked in the Jakarta EE 9 CI, Jakarta EE 9 Web Profile CI, and Jakarta -EE 9 Platform TCK in conjunction with various XML files containing Ant targets. +EE 9 TCK in conjunction with various XML files containing Ant targets. These Ant targets provide a convenient way to automate various configuration tasks for Jakarta EE 9 Platform TCK. For example, the initial configuration of the Jakarta EE 9 CI or Jakarta EE 9 Web Profile CI for TCK is @@ -426,7 +424,7 @@ is available on the Apache Ant Project license page at ~~~~~~~~~~~~~~~~~~~~~~~~~ The following section lists the hardware requirements for the Jakarta EE 9 -CTS software, using the Jakarta EE 9 CI or Jakarta EE 9 Web Profile CI. +TCK software, using the Jakarta EE 9 CI or Jakarta EE 9 Web Profile CI. Hardware requirements for other compatible implementations will vary. All systems should meet the following recommended hardware requirements: @@ -463,7 +461,7 @@ Linux software that meet the following software requirements: [[GEVCL]][[additional-jakarta-ee-9-platform-tck-requirements]] 1.5 Additional Jakarta EE 9 Platform TCK Requirements -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ In addition to the instructions and requirements described in this document, all Jakarta EE 9 and Jakarta EE 9 Web Profile implementations must @@ -485,7 +483,7 @@ specification at `https://jakarta.ee/specifications/bean-validation/3.0/` [[GBFQW]][[getting-started-with-the-jakarta-ee-9-platform-tck-test-suite]] 1.6 Getting Started With the Jakarta EE 9 Platform TCK Test Suite -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Installing, configuring, and using the Jakarta EE 9 Platform TCK involves the following general steps: @@ -494,8 +492,8 @@ following general steps: Profile CI. For example Eclipse GlassFish 6.0. 2. Download and install the Jakarta EE 9 Platform TCK package. 3. Configure your database to work with your CI. -4. Configure CTS to work with your database and CI. -5. Run the CTS tests. +4. Configure TCK to work with your database and CI. +5. Run the TCK tests. The remainder of this guide explains these steps in detail. If you just want to get started quickly with the Jakarta EE 9 Platform TCK using the most basic diff --git a/user_guides/jakartaee/src/main/jbake/content/jaspic-files.adoc b/user_guides/jakartaee/src/main/jbake/content/jaspic-files.adoc index 4c7b828696..59dd0ec3e1 100644 --- a/user_guides/jakartaee/src/main/jbake/content/jaspic-files.adoc +++ b/user_guides/jakartaee/src/main/jbake/content/jaspic-files.adoc @@ -7,9 +7,9 @@ prev=commonappdeploy.html Jakarta Authentication Technology Notes and Files ================================================== -[[GLAEQ]][[c-jakarta-authentication-technology-notes-and-files]] +[[GLAEQ]][[b-jakarta-authentication-technology-notes-and-files]] -C Jakarta Authentication Technology Notes and Files +B Jakarta Authentication Technology Notes and Files --------------------------------------------------- The Jakarta Authentication (formerly jaspic) technology tests are used to verify the compatibility of an @@ -25,16 +25,16 @@ run the Jakarta Authentication tests. After running the Jakarta Authentication t `ant disable.jaspic` command to restore the Jakarta EE 9 CI to the state it was in before you configured it for running the Jakarta Authentication tests. This is required because Jakarta Authentication replaces some of the Jakarta EE 9 CI's default -system security components with CTS security components. If this change +system security components with TCK security components. If this change is not reverted after the tests have been run, the CI's system security -could be left in a partially working state. The CTS security +could be left in a partially working state. The TCK security `AuthConfigFactory` and `AuthConfigProvider`(s) are designed for compatibility testing, not the functional completeness that one expects from the Jakarta EE 9 CI. -[[GLAFO]][[c.1-jakarta-authentication-1.1-technology-overview]] +[[GLAFO]][[b.1-jakarta-authentication-1.1-technology-overview]] -C.1 Jakarta Authentication 1.1 Technology Overview +B.1 Jakarta Authentication 1.1 Technology Overview ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The Jakarta Authentication 1.1 specification defines a service provider @@ -98,29 +98,29 @@ contains the Jakarta Authentication log file processor, which writes output to t `TSSVLog.txt` file. The `TSSVLog.txt` file is put into the location defined by the `log.file.location` property in the `ts.jte` file. -[[GLAFE]][[c.2-jakarta-authentication-tssv-files]] +[[GLAFE]][[b.2-jakarta-authentication-tssv-files]] -C.2 Jakarta Authentication TSSV Files +B.2 Jakarta Authentication TSSV Files ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The following sections describe the `tssv.jar`, `ProviderConfiguration.xml`, and `provider-configuration.dtd` files that are used by the Jakarta Authentication TCK tests. -[[GLAGR]][[c.2.1-tssv.jar-file]] +[[GLAGR]][[b.2.1-tssv.jar-file]] -C.2.1 tssv.jar file +B.2.1 tssv.jar file ^^^^^^^^^^^^^^^^^^^ The `tssv.jar` file contains classes necessary for populating your -implementation with a CTS AuthConfigFactory (ACF) as well as information -used to register CTS providers. The tssv.jar file contains the class +implementation with a TCK AuthConfigFactory (ACF) as well as information +used to register TCK providers. The tssv.jar file contains the class files for the Test Suite SPI Verifier. The `tssv.jar` file classes need to be loaded by your implementation's runtime during startup. -[[GLADE]][[c.2.2-providerconfiguration.xml-file]] +[[GLADE]][[b.2.2-providerconfiguration.xml-file]] -C.2.2 ProviderConfiguration.xml file +B.2.2 ProviderConfiguration.xml file ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The format of the `ProviderConfiguration.xml` file is a test @@ -159,9 +159,9 @@ done by setting the `traceflag` property in the `ts.jte` file and the application context identifier information should appear in the debug output. -[[GLAFZ]][[c.2.3-provider-configuration.dtd-file]] +[[GLAFZ]][[b.2.3-provider-configuration.dtd-file]] -C.2.3 provider-configuration.dtd file +B.2.3 provider-configuration.dtd file ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The `provider-configuration.dtd` file is a DTD file that resides in the diff --git a/user_guides/jakartaee/src/main/jbake/content/jms-resource-adaptr.adoc b/user_guides/jakartaee/src/main/jbake/content/jms-resource-adaptr.adoc index 44cf623602..e304b21cb3 100644 --- a/user_guides/jakartaee/src/main/jbake/content/jms-resource-adaptr.adoc +++ b/user_guides/jakartaee/src/main/jbake/content/jms-resource-adaptr.adoc @@ -6,9 +6,9 @@ prev=contextrootmappingrules.html Testing a Standalone Jakarta Messaging Resource Adapter ======================================================= -[[CJGFHFIF]][[g-testing-a-standalone-jakarta-messaging-resource-adapter]] +[[CJGFHFIF]][[f-testing-a-standalone-jakarta-messaging-resource-adapter]] -G Testing a Standalone Jakarta Messaging Resource Adapter +F Testing a Standalone Jakarta Messaging Resource Adapter --------------------------------------------------------- This appendix explains how to set up and configure a Jakarta EE 9 CI and @@ -28,12 +28,12 @@ Jakarta Messaging MDB and Resource Adapter Tests] * link:#CJGCDGIG[Reconfiguring Jakarta EE 9 CI for Jakarta EE 9 Platform TCK After Testing the Standalone Jakarta Messaging Resource Adapter] -[[CJGGIEEJ]][[g.1-setting-up-your-environment]] +[[CJGGIEEJ]][[f.1-setting-up-your-environment]] -G.1 Setting Up Your Environment +F.1 Setting Up Your Environment ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -Before you can run the Jakarta Messaging CTS tests against a standalone Jakarta Messaging Resource +Before you can run the Jakarta Messaging TCK tests against a standalone Jakarta Messaging Resource Adapter using a Jakarta EE 9 CI, you must install the following components: @@ -54,10 +54,10 @@ installed directories: JAVA_HOME/bin, JAVAEE_HOME/bin, TS_HOME/bin, and ANT_HOME/bin. -[[CJGDJCEC]][[g.2-configuring-java-ee-8-cts]] +[[CJGDJCEC]][[f.2-configuring-jakarta-ee-9-platform-tck]] -G.2 Configuring Jakarta EE 9 Platform TCK -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +F.2 Configuring Jakarta EE 9 Platform TCK +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The `ts.jte` file includes properties that must be set for testing a standalone Jakarta Messaging Resource Adapter using the Jakarta EE 9 CI. The Jakarta Messaging Resource @@ -87,18 +87,18 @@ your Jakarta EE 9 environment when the `config.vi` Ant task, which is described in the next section, is invoked. For the Jakarta EE 9 CI Eclipse GlassFish 6.0, the file is copied to the `JAVAEE_HOME/lib` directory. -[[CJGFCJBA]][[g.3-configuring-the-jakarta-ee-8-CI-for-the-standalone-jakarta-messaging-resource-adapter]] +[[CJGFCJBA]][[f.3-configuring-the-jakarta-ee-8-CI-for-the-standalone-jakarta-messaging-resource-adapter]] -G.3 Configuring a Jakarta EE 9 CI for the Standalone Jakarta Messaging Resource Adapter +F.3 Configuring a Jakarta EE 9 CI for the Standalone Jakarta Messaging Resource Adapter ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -Invoke the config.vi Ant task to configure the Jakarta EE 9 CI, Eclipse GlassFish 6.0 for CTS 9 +Invoke the config.vi Ant task to configure the Jakarta EE 9 CI, Eclipse GlassFish 6.0 for TCK 9 and the standalone Jakarta Messaging Resource Adapter: 1. Change to the `TS_HOME/bin` directory. 2. Execute the `config.vi` Ant task. + The config.vi Ant task executes scripts, which configure your Jakarta EE 9 -environment for CTS 9. One of the ant scripts that gets executed will +environment for TCK 9. One of the ant scripts that gets executed will configure and deploy the standalone Jakarta Messaging Resource Adapter, copy the JAR file containing the classes for the standalone Jakarta Messaging Resource Adapter to the `JAVAEE_HOME/lib` directory, create the Jakarta Messaging connector connect ion @@ -117,9 +117,9 @@ for that environment. If you are using a different standalone Jakarta Messaging resource adapter, you will need to rewrite these scripts for that Jakarta Messaging resource adapter. -[[CJGEBECH]][[g.4-modifying-the-runtime-deployment-descriptors-for-the-jakarta-messaging-mdb-and-resource-adapter-tests]] +[[CJGEBECH]][[f.4-modifying-the-runtime-deployment-descriptors-for-the-jakarta-messaging-mdb-and-resource-adapter-tests]] -G.4 Modifying the Runtime Deployment Descriptors for the Jakarta Messaging MDB and Resource Adapter Tests +F.4 Modifying the Runtime Deployment Descriptors for the Jakarta Messaging MDB and Resource Adapter Tests ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ After the standalone Jakarta Messaging Resource Adapter has been configured and @@ -152,9 +152,9 @@ runtime deployment descriptor XML files will need to be vendor specific. In this case, you will need to modify the Ant script to handle your vendor-specific runtime deployment descriptor XML files. -[[CJGFHCBJ]][[g.5-running-the-jakarta-messaging-tests-from-the-command-line]] +[[CJGFHCBJ]][[f.5-running-the-jakarta-messaging-tests-from-the-command-line]] -G.5 Running the Jakarta Messaging Tests From the Command Line +F.5 Running the Jakarta Messaging Tests From the Command Line ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Run the Jakarta Messaging tests: @@ -163,9 +163,9 @@ Run the Jakarta Messaging tests: . Invoke the `runclient` Ant target: + `ant runclient` -[[CJGCJGIH]][[g.6-restoring-the-runtime-deployment-descriptors-for-the-jakarta-messaging-mdb-and-resource-adapter-tests]] +[[CJGCJGIH]][[f.6-restoring-the-runtime-deployment-descriptors-for-the-jakarta-messaging-mdb-and-resource-adapter-tests]] -G.6 Restoring the Runtime Deployment Descriptors for the Jakarta Messaging MDB and Resource Adapter Tests +F.6 Restoring the Runtime Deployment Descriptors for the Jakarta Messaging MDB and Resource Adapter Tests ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ After you run the Jakarta Messaging tests against your standalone Jakarta Messaging Resource @@ -184,10 +184,10 @@ descriptor XML files will be vendor specific. In this case, you will need to modify the Ant script to handle the vendor-specific runtime deployment descriptor XML files appropriate for your environment. -[[CJGCDGIG]][[g.7-reconfiguring-jakarta-ee-8-CI-for-jakarta-ee-8-cts-after-testing-the-standalone-jakarta-messaging-resource-adapter]] +[[CJGCDGIG]][[f.7-reconfiguring-jakarta-ee-8-CI-for-jakarta-ee-9-platform-tck-after-testing-the-standalone-jakarta-messaging-resource-adapter]] -G.7 Reconfiguring Jakarta EE 9 CI for Jakarta EE 9 Platform TCK After Testing the Standalone Jakarta Messaging Resource Adapter -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +F.7 Reconfiguring Jakarta EE 9 CI for Jakarta EE 9 Platform TCK After Testing the Standalone Jakarta Messaging Resource Adapter +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ After you finish testing the standalone Jakarta Messaging Resource Adapter, you need to reconfigure the Jakarta EE 9 CI before you can continue testing with diff --git a/user_guides/jakartaee/src/main/jbake/content/portingpackage.adoc b/user_guides/jakartaee/src/main/jbake/content/portingpackage.adoc index 760a5183d5..c600edc43f 100644 --- a/user_guides/jakartaee/src/main/jbake/content/portingpackage.adoc +++ b/user_guides/jakartaee/src/main/jbake/content/portingpackage.adoc @@ -25,8 +25,6 @@ Edition server environment. You also need to create a deployment plan for each deployable component (EAR, EJB JAR, WAR, and RAR files) in the test suite as defined by the Jakarta Platform, Enterprise Edition platform. -======================================================================= - [[GFASD]][[overview]] @@ -112,7 +110,7 @@ permitted to exit the VM (for example, by using the `System.exit` call). 11.2 Porting Package APIs ~~~~~~~~~~~~~~~~~~~~~~~~~ -The following sections describe the API in the Jakarta EE 9 Platform TCK porting +The following sections describe the API in the Jakarta EE 9 CTS porting package. The implementation classes used with the Jakarta Platform, Enterprise Edition CI are located in the `/src/com/sun/ts/lib/implementation/sun/javaee` directory. You @@ -123,14 +121,14 @@ Detailed API documentation for the porting package interfaces is available in the `/docs/api` directory. The API included in this section are: -* link:#GFASM[TSDeploymentInterface2] +* link:#GFASM[TSDeploymentInterface2 is removed] * link:#GKLJO[Ant-Based Deployment Interface] * link:#GFASI[TSJMSAdminInterface] * link:#GFATH[TSLoginContextInterface] * link:#GFATO[TSURLInterface] * link:#GFASJ[TSHttpsURLConnectionInterface] -[[GFASM]][[tsdeploymentinterface2]] +[[GFASM]][[tsdeploymentinterface2-is-removed]] 11.2.1 TSDeploymentInterface2 is removed ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ @@ -142,8 +140,6 @@ which uses only the standard Deployment APIs defined by the Jakarta Platform, Enterprise Edition platform. The following properties are still in the `ts.jte` file to reflect this and should not be changed: ----- - [[GKLJO]][[ant-based-deployment-interface]] 11.2.2 Ant-Based Deployment Interface diff --git a/user_guides/jakartaee/src/main/jbake/content/rules-wp.adoc b/user_guides/jakartaee/src/main/jbake/content/rules-wp.adoc index 4ed81f2453..7ec9ac58b1 100644 --- a/user_guides/jakartaee/src/main/jbake/content/rules-wp.adoc +++ b/user_guides/jakartaee/src/main/jbake/content/rules-wp.adoc @@ -443,7 +443,7 @@ Compatibility Kits (TCKs): * Jakarta Dependency Injection 2.0 * Jakarta Bean Validation 3.0 -In addition to the compatibility rules outlined in this CTS User's +In addition to the compatibility rules outlined in this TCK User's Guide, Jakarta EE 9 implementations must also adhere to all of the compatibility rules defined in the User's Guides of the aforementioned TCKs. @@ -468,7 +468,7 @@ source code that does not conform to the Java Language Specification Jakarta has a well established process for managing challenges to its TCKs. Any implementor may submit a challenge to one or more tests in the -Jakarta EE Version 9 TCK (AKA CTS) as it relates to their implementation. Implementor +Jakarta EE Version 9 TCK as it relates to their implementation. Implementor means the entity as a whole in charge of producing the final certified release. *Challenges filed should represent the consensus of that entity*. diff --git a/user_guides/jakartaee/src/main/jbake/content/rules.adoc b/user_guides/jakartaee/src/main/jbake/content/rules.adoc index eb65d6d0ac..fea7bbddb8 100644 --- a/user_guides/jakartaee/src/main/jbake/content/rules.adoc +++ b/user_guides/jakartaee/src/main/jbake/content/rules.adoc @@ -453,13 +453,13 @@ programmatic behavior of the Runtime to vary from the functional programmatic behavior of the Runtime in the absence of that comment. EE21 Compliance testing for Jakarta EE 9 consists of running Jakarta EE 9 -CTS and the following Technology Compatibility Kits (TCKs): +TCK and the following Technology Compatibility Kits (TCKs): * Jakarta Contexts and Dependency Injection 3.0 * Jakarta Dependency Injection 2.0 * Jakarta Bean Validation 3.0 -In addition to the compatibility rules outlined in this CTS User's +In addition to the compatibility rules outlined in this TCK User's Guide, Jakarta EE 9 implementations must also adhere to all of the compatibility rules defined in the User's Guides of the aforementioned TCKs. @@ -484,7 +484,7 @@ source code that does not conform to the Java Language Specification Jakarta has a well established process for managing challenges to its TCKs. Any implementor may submit a challenge to one or more tests in the -Jakarta EE version 9 TCK (AKA CTS) as it relates to their implementation. Implementor +Jakarta EE version 9 TCK as it relates to their implementation. Implementor means the entity as a whole in charge of producing the final certified release. *Challenges filed should represent the consensus of that entity*. diff --git a/user_guides/jakartaee/src/main/jbake/content/title.adoc b/user_guides/jakartaee/src/main/jbake/content/title.adoc index de61d3d849..66a1e05d21 100644 --- a/user_guides/jakartaee/src/main/jbake/content/title.adoc +++ b/user_guides/jakartaee/src/main/jbake/content/title.adoc @@ -5,7 +5,7 @@ next=TCKpreface.html prev=toc.html ~~~~~~ Jakarta EE Platform, Enterprise Edition 9 Test Compatibility Kit User's Guide, Release 9 for Jakarta EE -========================================================================================================= +======================================================================================================= [[oracle]] Eclipse Foundation™ @@ -16,11 +16,11 @@ Guide Release 9 for Jakarta EE -October, 2020 +November, 2020 Provides detailed instructions for obtaining, installing, configuring, -and using the Eclipse Jakarta, Enterprise Edition 9 Test Compatibility Kit - for the Full Profile and the Web Profile. +and using the Eclipse Jakarta, Enterprise Edition 9 Compatibility Test +Suite for the Full Profile and the Web Profile. [[sthref1]] diff --git a/user_guides/jakartaee/src/main/jbake/content/toc.adoc b/user_guides/jakartaee/src/main/jbake/content/toc.adoc index 063b4a364f..5990e1ab80 100644 --- a/user_guides/jakartaee/src/main/jbake/content/toc.adoc +++ b/user_guides/jakartaee/src/main/jbake/content/toc.adoc @@ -1,10 +1,10 @@ type=page status=published -title=Jakarta EE Platform, Enterprise Edition 9 Compatibility Test Suite User's Guide, Release 9 for Jakarta EE +title=Jakarta EE Platform, Enterprise Edition 9 Test Compatibility Kit User's Guide, Release 9 for Jakarta EE next=title.html ~~~~~~ -Jakarta EE Platform, Enterprise Edition 9 Compatibility Test Suite User's Guide, Release 9 for Jakarta EE -========================================================================================================= +Jakarta EE Platform, Enterprise Edition 9 Test Compatibility Kit User's Guide, Release 9 for Jakarta EE +======================================================================================================= [[contents]] Contents diff --git a/user_guides/jakartaee/src/main/jbake/content/troubleshooting.adoc b/user_guides/jakartaee/src/main/jbake/content/troubleshooting.adoc index a254c0ad73..d97e461a1a 100644 --- a/user_guides/jakartaee/src/main/jbake/content/troubleshooting.adoc +++ b/user_guides/jakartaee/src/main/jbake/content/troubleshooting.adoc @@ -22,7 +22,7 @@ Test Suite. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This section lists common problems that you may encounter as you run the -Jakarta Platform, Enterprise Edition Compatibility Test Suite software on +Jakarta Platform, Enterprise Edition Test Compatibility Kit software on the Jakarta Platform, Enterprise Edition CI, Eclipse GlassFish 6.0. It also proposes resolutions for the problems, where applicable. diff --git a/user_guides/jakartaee/src/main/jbake/content/using.adoc b/user_guides/jakartaee/src/main/jbake/content/using.adoc index a91d2872f6..94e5bb89a4 100644 --- a/user_guides/jakartaee/src/main/jbake/content/using.adoc +++ b/user_guides/jakartaee/src/main/jbake/content/using.adoc @@ -37,10 +37,10 @@ respectively. ======================================================================= -[[GFADX]][[jakarta-ee-8-cts-operating-assumptions]] +[[GFADX]][[jakarta-ee-9-platform-tck-operating-assumptions]] 7.1 Jakarta EE 9 Platform TCK Operating Assumptions -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The following are assumed in this chapter: @@ -100,7 +100,7 @@ for detailed configuration instructions. ---- ant gui ---- -Using the JavaTest GUI to run CTS tests is described later in this +Using the JavaTest GUI to run TCK tests is described later in this guide. For detailed information about using the JavaTest interface, see the JavaTest User's Guide. + @@ -336,12 +336,12 @@ Note that multiple `priorStatus` values must be separated by commas. 7.5 Using Keywords to Test Required and Optional Technologies ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -The Jakarta EE CTS includes some tests that may be optional depending on +The Jakarta EE TCK includes some tests that may be optional depending on your implementation. For example, certain technologies are now optional for implementations of the full Jakarta EE Platform. There are other technologies which are optional for Web Profile implementations, but may be implemented. If implemented, optional tests must be run and pass. -There are two mechanisms in place in the CTS which control whether or +There are two mechanisms in place in the TCK which control whether or not a given set of tests is run - the `javaee.level` property in the `ts.jte` file (see link:#BCGBAHFF[Section 7.5.1, "Setting the javaee.level Property"]) and keywords (see link:#BCGHGJIC[Section 7.5.2, @@ -375,7 +375,7 @@ javaee.level=full 7.5.2 Using Keywords to Create Groups and Subsets of Tests ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -Each test in CTS has keywords associated with it. The keywords are used +Each test in TCK has keywords associated with it. The keywords are used to create groups and subsets of tests. At test execution time, a user can tell the test harness to only run tests with or without certain keywords. This mechanism is used to select or omit testing on selected @@ -396,7 +396,7 @@ the test tree. The examples in the sections that follow show how to use keywords to run required technologies in both the Full and Web profile, run/omit running -optional sets of tests in CTS, and run the Interoperability and +optional sets of tests in TCK, and run the Interoperability and Rebuildable tests in forward and reverse directions. [[sthref26]][[to-use-keywords-to-run-required-technologies]] @@ -579,17 +579,17 @@ ant -Dkeywords="javaee_web_profile | jacc_web_profile | jaspic_web_profile" runc 7.5.2.4 To Use Keywords to Run Optional Subsets for Jakarta Enterprise Beans Lite +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -Table 1-1 shows the CTS keywords you can use to test optional Jakarta Enterprise Beans (formerly EJB) Lite +Table 1-1 shows the TCK keywords you can use to test optional Jakarta Enterprise Beans (formerly EJB) Lite components. Components denoted with an asterisk (*) are pruned components; components without an asterisk are not required by EJB Lite. [[sthref41]][[sthref42]] -===== Table 7-3 CTS Keywords for Optional Jakarta Enterprise Beans Lite Components +===== Table 7-3 TCK Keywords for Optional Jakarta Enterprise Beans Lite Components [width="100%",cols="50%,50%",options="header",] |======================================================================= -|Component |CTS Keyword +|Component |TCK Keyword |Message-Driven Beans |`ejb_mdb_optional` |1x CMP/BMP Entity Beans * |ejb_1x_optional @@ -723,7 +723,7 @@ directions must pass. If you are running Interop or XML Web Service reverse tests, which run against the Jakarta EE 9 CI, you must start the standalone deployment -server in a separate shell on the same host as the CTS harness. The +server in a separate shell on the same host as the TCK harness. The default deployment porting implementation goes through a standalone deployment server with a dedicated classpath. To start the standalone deployment server, change to the `/bin` directory and execute @@ -749,7 +749,7 @@ The `com/sun/ts/tests/jms/ee20/resourcedefs` directory must also be rebuilt. Run the `build.special.webservices.clients` Ant target to rebuild the tests in this directory. -The database properties in the CTS bundle are set to Derby database. If +The database properties in the TCK bundle are set to Derby database. If any other database is used, the `update.metadata.token.values` ant target needs to be executed for metadata-complete tests.