impl.vi.deploy.dir=${webcontainer.home}/domains/domain1/autodeploy
impl.vi=glassfish.xml
impl.vi.host=${webServerHost}
impl.vi.port=${webServerPort}
Setup and Configuration |
Previous | Next | Contents |
Note
|
The Jakarta EE Specification process provides for any number of compatible implementations. As additional implementations become available, refer to project or product documentation from those vendors for specific TCK setup and operational guidance. |
This chapter describes how to set up the XML Web Services TCK and JavaTest harness software. Before proceeding with the instructions in this chapter, be sure to install all required software, as described in Chapter 3, "Installation."
After completing the instructions in this chapter, proceed to Chapter 5, "Executing Tests," for instructions on running the XML Web Services TCK.
After configuring your environment as described in this section, continue with the instructions in Section 4.6, "Using the JavaTest Harness Software."
Note
|
In these instructions, variables in angle brackets need to be expanded
for each platform. For example, On Windows, you must escape any backslashes with an extra backslash in path separators used in any of the following properties, or use forward slashes as a path separator instead. |
Set the following environment variables in your shell environment:
JAVA_HOME
to the directory in which Java SE 8 is installed
TS_HOME
to the directory in which the XML Web Services TCK
2.3 software is installed
PATH
to include the following directories: JAVA_HOME/bin
,
JAXWS_HOME/bin
, and <TS_HOME>/tools/ant/bin
Edit your <TS_HOME>/bin/ts.jte
file and set the following
environment variables:
Set the webServerHost
property to the hostname where the web
server is running that is configured with the JAX-WS RI.
The default setting is localhost
.
Set the webServerPort
property to the port number where the web
server is running that is configured with the JAX-WS RI.
The default setting is 8000
.
Set the jaxws.home
property to the location where the JAX-WS RI is
installed.
The default setting is ${webcontainer.home}
. The value of this
property must match the value of the webcontainer.home
property that
is set in step g.
Set the jaxws.classes
property to point to the JAX-WS RI
classes/jars.
Note that this property is already set and should not require any
changes.
Verify that the tools.jar
property is set to the location of the
tools.jar
file that is distributed with Java SE.
Set the
impl.vi, impl.vi.deploy.dir, impl.vi.host, and impl.vi.port
properties
to the supported web container, deploy directory, host and port for the
JAX-WS RI.
The supported web container for the JAX-WS RI is the Java EE 8 RI. So
the default settings for these properties are as follows:
impl.vi.deploy.dir=${webcontainer.home}/domains/domain1/autodeploy
impl.vi=glassfish.xml
impl.vi.host=${webServerHost}
impl.vi.port=${webServerPort}
Set the webcontainer.home
property to the location where the web
server is installed for the JAX-WS RI. This will be where the Java EE 8
RI is installed.
Set the porting.ts.url.class.1
property to the porting
implementation class that is used for obtaining URLs.
The default setting for the JAX-WS RI porting implementation is:
com.sun.ts.lib.implementation.sun.common.SunRIURL
Set the user
and password
properties to the user name and
password used for the basic authentication tests.
The default setting is j2ee
for both.
Set the authuser
and authpassword
properties to the user name
and password used for the basic authentication tests.
The default setting for both is javajoe
.
Set the http.server.supports.endpoint.publish
property based on
whether Endpoint Publish APIs are supported on the container.
If using Java SE 8 or above, verify that the property
endorsed.dirs
is set to the location of the VI API jars for those
technologies you wish to override. Java SE 8 contains an implementation
of JAX-WS 2.2 which will conflict with JAX-WS 2.3, therefore this
property must be set so that JAX-WS 2.3 will be used during the building
of tests and during test execution.
Edit the catalog file
<TS_HOME>/src/com/sun/ts/tests/jaxws/common/xml/catalog /META-INF/jax-ws-catalog.xml
,
replacing the host and port settings of systemId
with the value of
your host and port setting where the WSDL is published.
After configuring your environment as described in this section, continue with the instructions in Section 4.4, "Using the JavaTest Harness Software."
Note
|
In these instructions, variables in angle brackets need to be expanded
for each platform. For example, On Windows, you must escape any backslashes with an extra backslash in path separators used in any of the following properties, or use forward slashes as a path separator instead. |
Before You Begin
Decide against which XML Web Services implementation the tests will be run and determine to which Servlet–compliant Web server the XML Web Services TCK applications will be published.
Package the XML Web Services test applications for that XML Web Services implementation and Servlet–compliant Web server.
See Appendix B, "Packaging the Test Applications in Servlet-Compliant WAR Files With VI-Specific Information," for information about repackaging the XML Web Services test application.
Set the following environment variables in your shell environment:
JAVA_HOME
to the directory in which Java SE 8 is installed
TS_HOME
to the directory in which the XML Web Services TCK
2.3 software is installed
PATH
to include the following directories: JAVA_HOME/bin
,
JAXWS_HOME/bin
, and <TS_HOME>/tools/ant/bin
Edit your <TS_HOME>/bin/ts.jte
file and set the following
environment variables:
Set the webServerHost
property to the hostname where the web
server that is configured with the Vendor Implementation is running.
The default setting is localhost
.
Set the webServerPort
property to the port number where the web
server that is configured with the Vendor Implementation is running.
The default setting is 8080
.
Set the jaxws.home
property to the location where the Vendor
Implementation is installed.
The default setting is ${webcontainer.home}
. The value of this
property must match the value of the webcontainer.home
property that
is set in step g.
Set the jaxws.classes
property to point to the Vendor
Implementation classes/JAR files.
As an example, the ts.jte
file contains the property
jaxws.classes.ri
, which contains the classes/jar files that the Java
EE 8 RI uses. The jaxws.classes.ri
settings for the Java EE 8 RI web
container are as follows:
jaxws.home.ri=${webcontainer.home.ri}
jaxws.lib.ri=${jaxws.home.ri}/modules
endorsed.dirs.ri=${jaxws.home.ri}/modules/endorsed
jaxws.classes.ri=${endorsed.dirs.ri}/webservices-api-osgi.jar:
${endorsed.dirs.ri}/jaxb-api-osgi.jar:
${jaxws.lib.ri}/webservices-osgi.jar:
${jaxws.lib.ri}/jaxb-osgi.jar:
${jaxws.lib.ri}/gmbal.jar:
${jaxws.lib.ri}/management-api.jar:
${jaxws.lib.ri}/mimepull.jar
The jaxws.classes.ri
settings if using the Apache Tomcat web container
with the Standalone JAX-WS 2.3 RI would be as follows:
jaxws.home.ri=${webcontainer.home.ri}
jaxws.lib.ri=${jaxws.home.ri}/shared/lib
endorsed.dirs.ri=${jaxws.home.ri}/common/endorsed
jaxws.classes.ri=${endorsed.dirs.ri}/jaxws-api.jar:
${endorsed.dirs.ri}/jaxb-api.jar:
${jaxws.lib.ri}/FastInfoset.jar:${jaxws.lib.ri}/gmbal-api-only.jar:\
${jaxws.lib.ri}/ha-api.jar:${jaxws.lib.ri}/javax.annotation-api.jar:\
${jaxws.lib.ri}/javax.xml.soap-api.jar:${jaxws.lib.ri}/jaxb-core.jar:\
${jaxws.lib.ri}/jaxb-impl.jar:${jaxws.lib.ri}/jaxb-jxc.jar:\
${jaxws.lib.ri}/jaxb-xjc.jar:${jaxws.lib.ri}/jaxws-rt.jar:\
${jaxws.lib.ri}/jaxwstck.jar:${jaxws.lib.ri}/jaxws-tools.jar:\
${jaxws.lib.ri}/jsr181-api.jar:${jaxws.lib.ri}/mail.jar:\
${jaxws.lib.ri}/management-api.jar:${jaxws.lib.ri}/mimepull.jar:\
${jaxws.lib.ri}/policy.jar:${jaxws.lib.ri}/resolver.jar:\
${jaxws.lib.ri}/saaj-impl.jar:${jaxws.lib.ri}/sdo-eclipselink-plugin.jar:\
${jaxws.lib.ri}/stax2-api.jar:${jaxws.lib.ri}/stax-ex.jar:\
${jaxws.lib.ri}/streambuffer.jar:${jaxws.lib.ri}/woodstox-core-asl.jar:
Verify that the tools.jar
property is set to the location of the
tools.jar
file that is distributed with Java SE.
Set the impl.vi
, impl.vi.deploy.dir
, impl.vi.host
, and
impl.vi.port
properties to the supported web container, deploy
directory, host and port for the Vendor Implementation.
As an example, the ts.jte
file contains the settings for the Java EE 8
RI, which are as follows:
webcontainer.home.ri=/sun/javaee6
impl.ri.deploy.dir=${webcontainer.home.ri}/domains/domain1/autodeploy
impl.ri=glassfish.xml
impl.ri.host=${webServerHost.2}
impl.ri.port=${webServerPort.2}
The RI settings using the Apache Tomcat web container with the Standalone JAX-WS 2.3 RI would be as follows:
webcontainer.home.ri=/tomcat
impl.ri=tomcat
impl.ri.deploy.dir=${webcontainer.home.ri}/webapps
impl.ri.host=${webServerHost.2}
impl.ri.port=${webServerPort.2}
Set the webcontainer.home
property to the location where the web
container for the Vendor Implementation is installed.
Set the porting.ts.url.class.1
property to the porting
implementation class that is used for obtaining URLs.
The default setting for the JAX-WS RI porting implementation is:
com.sun.ts.lib.implementation.sun.common.SunRIURL
Set the user
and password
properties to the user name and
password used for the basic authentication tests.
The default setting for both is j2ee
.
Set the authuser
and authpassword
properties to the user name
and password used for the basic authentication tests.
The default setting for both is javajoe
.
Set the http.server.supports.endpoint.publish
property based on
whether Endpoint Publish APIs are supported on the container.
If using Java SE 8 or above, verify that the property
endorsed.dirs
is set to the location of the RI API jars for those
technologies you wish to override. Java SE 8 contains an implementation
of JAX-WS 2.2 which will conflict with JAX-WS 2.3, therefore this
property must be set so that JAX-WS 2.3 will be used during the building
of tests and during test execution.
Edit the catalog file
<TS_HOME>/src/com/sun/ts/tests/jaxws/common/xml/catalog /META-INF/jax-ws-catalog.xml
,
replacing the host and port settings of systemId
with the value of
your host and port setting where the WSDL is published.
Provide your own implementation of the porting package interface
provided with the JAX-WS TCK.
The porting package interface, TSURLInterface.java
, obtains URL
strings for web resources in an implementation-specific manner. API
documentation for the TSURLInterface.java
porting package interface is
available in the JAX-WS TCK documentation bundle.
The <TS_HOME>/bin/jaxws-url-props.dat
file contains the webservice
endpoint and WSDL URLs that the TCK tests use when running against the
JAX-WS RI. In the porting package that the TCK uses, the URLs are
returned as is since this is the form that the JAX-WS RI expects. You
may need an alternate form of these URLs in order to run the TCK tests
in your environment. However, you MUST NOT modify the
jaxws-url-props.dat
file, but instead make any necessary changes in
your own porting implementation class to transform the URLs
appropriately for your environment.
This section describes the steps needed to configure the JAX-WS TCK so that the tests can be rebuilt (using the Vendor Implementation toolset), and then deployed and run against the JAX-WS Reference Implementation.
If you are not ready to proceed with this portion of the testing process, skip this section for now and proceed to Configuring and Starting Your Application Server or Servers. After configuring your environment, continue with the instructions in Using the JavaTest Harness Software.
Note
|
In these instructions, variables in angle brackets need to be expanded
for each platform. For example, On Windows, you must escape any backslashes with an extra backslash in
path separators used in any of the following properties, or use forward
slashes as a path separator instead. For example, if the Java EE 8 RI
installation is |
Set the following environment variables in your shell environment:
JAVA_HOME
to the directory in which Java SE is installed
TS_HOME
to the directory in which the JAX-WS TCK 2.3 software is
installed
ANT_HOME
should not be set in your environment. If it is set,
unset it.
Edit your <TS_HOME>/bin/ts.jte
file and set the following
environment variables:
Set the webServerHost
property to the hostname where the web
server for the Vendor Implementation is running.
The default setting is localhost
.
Set the webServerPort
property to the port number where the web
server for the Vendor Implementation is running.
The default setting is`8080`
Set the webServerHost.2
property to the hostname where the web
server for the JAX-WS RI is running.
Set the webServerPort.2
property to the port number where the web
server for the JAX-WS RI is running.
Set the jaxws.home
property to the location where the Vendor
Implementation is installed.
The default setting is ${webcontainer.home}
. The value of this
property must match the value of the webcontainer.home
property that
is set in step m.
Set the jaxws.classes
property to point to the Vendor
Implementation classes/JAR files.
Set the jaxws.home.ri
property to the location where the JAX-WS RI
is installed.
The default setting is ${webcontainer.home.ri}
. The value of this
property must match the value of the webcontainer.home.ri
property
that is set in step n.
The jaxws.classes.ri
property is already configured to point to
the JAX-WS RI classes/JAR files.
No changes are necessary for this property.
Set the wsgen.ant.classname
property to the Vendor Implementation
class that mimics the JAX-WS RI Ant task, which in turn calls the
wsgen
Java-to-WSDL tool.
Set the wsimport.ant.classname
property to the Vendor
Implementation class that mimics the JAX-WS RI Ant task, which in turn
calls the wsimport
WSDL-to-Java tool.
Set the impl.vi
, impl.vi.deploy.dir
, impl.vi.host
, and
impl.vi.port
properties to the supported web container, deploy
directory, host and port used for the Vendor Implementation.
Set the impl.ri
, impl.ri.deploy.dir
, impl.ri.host
, and
impl.ri.port
properties to the supported web container, deploy
directory, host and port used for the JAX-WS Reference Implementation.
The supported web container for standalone web applications is the Java
EE 8 RI. The default settings for these properties are as follows:
impl.ri.deploy.dir=${webcontainer.home.ri}/domains/domain1/autodeploy
impl.ri=glassfish.xml
impl.ri.host=${webServerHost.2}
impl.ri.port=${webServerPort.2}
Set the webcontainer.home
property to the location where the web
container for the Vendor Implementation is installed.
Set the webcontainer.home.ri
property to the location where the web
container for the JAX-WS Reference Implementation is installed.
Set the porting.ts.url.class.1
property to your porting
implementation class that is used for obtaining URLs.
The default setting points to the JAX-WS RI porting implementation which
is:
com.sun.ts.lib.implementation.sun.common.SunRIURL
Set the porting.ts.url.class.2
property to the JAX-WS RI porting
implementation class that is used for obtaining URLs.
No changes are necessary for this property.
Set the user
and password
properties to the user name and
password used for the basic authentication tests.
The default setting for both is j2ee
.
Set the authuser
and authpassword
properties to the user name
and password used for the basic authentication tests.
The default setting for both is javajoe
.
Set the http.server.supports.endpoint.publish
property based on
whether Endpoint Publish APIs are supported on the container.
If using Java SE 8 or above, verify that the property
endorsed.dirs
is set to the location of the VI API jars for those
technologies you wish to override. Java SE 8 contains an implementation
of JAX-WS 2.2 which will conflict with JAX-WS 2.3, therefore this
property must be set so that JAX-WS 2.3 will be used during the building
of tests and during test execution.
If using Java SE 8 or above, verify that the property
endorsed.dirs.ri
is set to the location of the RI API jars for those
technologies you wish to override. Java SE 8 contains an implementation
of JAX-WS 2.2 which will conflict with JAX-WS 2.3, therefore this
property must be set so that JAX-WS 2.3 will be used during the building
of tests and during test execution.
Edit the catalog file
<TS_HOME>/src/com/sun/ts/tests/jaxws/common/xml/catalog /META-INF/jax-ws-catalog.xml
,
replacing the host and port settings of systemId
with the value of
your host and port setting where the WSDL is published.
This section describes the steps needed to configure the JAX-WS TCK so that all tests can be run; forward tests against the Vendor Implementation and reverse tests against the JAX-WS Reference Implementation.
Since the JAX-WS TCK needs to be tested against both the JAX-WS Reference Implementation and the Vendor Implementation, two separate Web servers need to be configured. Two individual Web servers are required, and the same steps, below, must be performed to configure each Web server.
If you are not going to perform this kind of testing at this time, skip this section and proceed to Configuring and Starting Your Application Server or Servers, otherwise perform the steps described in the following sections:
Complete the following two procedures to configure your application server environments for the RI and VI.
Set the following environment variables in your shell environment:
JAVA_HOME
to the directory in which Java SE is installed
TS_HOME
to the directory in which the JAX-WS TCK 2.3 software is
installed
ANT_HOME
should not be set in your environment. If it is set,
unset it.
Ensure that the ts.jte
settings for Vendor specific properties
have been configured.
Run the ant config.vi
target to configure for the Vendor
Implementation.
cd <TS_HOME>/bin
<TS_HOME>/tools/ant/bin/ant config.vi
Set the following environment variables in your shell environment:
JAVA_HOME
to the directory in which Java SE is installed
TS_HOME
to the directory in which the JAX-WS TCK 2.3 software is
installed
ANT_HOME
should not be set in your environment. If it is set,
unset it.
Ensure that the ts.jte
settings for RI specific properties have
been configured.
Run the ant config.ri
target to configure for RI implementation.
cd <TS_HOME>/bin
<TS_HOME>/tools/ant/bin/ant config.ri
The JAX-WS TCK provides an automatic way of deploying both the prebuilt and Vendor-built archives to the configured web container or container by using deployment handlers.
The handler file (<TS_HOME>/bin/xml/impl/glassfish/deploy.xml
) is
written to be used with the Java EE 8 RI. If the Vendor chooses not to
use Java EE 8 RI with their implementation, or chooses to rebuild the
JAX-WS TCK tests using some other method than the infrastructure
provided, they should create their own version handler file to provide
this functionality.
This section describes the various commands used for deploying the WAR files to the configured web container.
The keywords
system property enables you to deploy a subset of the
tests that would normally be deployed in batch mode by means of
<TS_HOME>/tools/ant/bin/ant deploy
. To specify it, add the option
-Dkeywords=`value to the `ant
command, where value is either
forward
, reverse
, or all
. The supported values control the
directions in which the rebuildable tests are deployed.
Setting this property to all
(the default) deploys both the prebuilt
and Vendor build tests.
Setting the property to forward
deploys the prebuilt tests in the
forward direction only.
Setting the property to reverse
deploys the Vendor rebuilt tests in
the reverse direction only.
<TS_HOME>/dist
Directory to Both Web ServersEnter the following command:
<TS_HOME>/tools/ant/bin/ant deploy.all
or
<TS_HOME>/tools/ant/bin/ant -Dkeywords=all deploy.all
Enter the following commands:
cd <TS_HOME>/src/com/sun/ts/tests/jaxws/api/javax_xml_ws/Dispatch
<TS_HOME>/tools/ant/bin/ant -Dkeywords=forward deploy
Enter the following commands:
cd <TS_HOME>/src/com/sun/ts/tests/jaxws/api
<TS_HOME>/tools/ant/bin/ant -Dkeywords=reverse deploy
Note
|
The |
This section explains issues regarding the deployment of the JAX-WS TCK prebuilt archives. Before conducting any deployment, ensure that your environment has been configured by following the instructions in either the Configuring Your Environment to Run the JAX-WS TCK Against the JAX-WS Reference Implementation or the Configuring Your Environment to Run the JAX-WS TCK Against the Vendor Implementation sections.
The <TS_HOME>/dist
directory contains all the WAR files for the JAX-WS
TCK web service endpoint tests that have been compiled and generated
using the JAX-WS Reference Implementation and packaged for deployment on
a Servlet-compliant web container using the standard Web Archive (WAR)
format.
These WAR files contain only portable artifacts for all the TCK web
service endpoint tests, and are tailored to run against the JAX-WS
Reference Implementation via the web.xml
file in addition to a runtime
file, sun-jaxws.xml
. These WAR files allow you to deploy (without any
additional setup or modification) against the JAX-WS Reference
Implementation to test the various features and functionality of this
implementation.
A Vendor is required to deploy the prebuilt WAR files as is on their
JAX-WS implementation without any changes to the WAR archives with the
exception of replacing and/or removing only the web.xml
and the
sun-jaxws.xml
files.
To deploy the tests, the Vendor should perform a deployment using either
the deploy
or deployall
batch command as described in
Generic Deployment Command Scenarios, and specify the
-Dkeywords=forward
option.
This section describes how to deploy the Vendor rebuilt JAX-WS TCK tests against the Vendor Implementation. Before conducting the deployment, ensure that you have followed the instructions in Configuring Your Environment to Run the JAX-WS TCK Against the JAX-WS Reference Implementation.
This deployment scenario assumes that the Vendor has rebuilt all the
JAX-WS TCK tests using the existing infrastructure, and that the WAR
files exist alongside the prebuilt war files in the <TS_HOME>/dist
directory. The rebuilt WAR files will be prepended with the text
vi_built_
.
If the Vendor chooses some other method of rebuilding the tests, they
may still be able to use this deployment method as long as the WAR files
are built correctly and are prepended with the text vi_built_
. Refer
to the Appendix B, "Rebuilding the JAX-WS TCK
Using the Vendor’s Toolset" to learn about rebuilding the JAX-WS TCK
tests.
To deploy the tests, the Vendor should perform a deployment using either
the deploy
or deployall
batch command, as described in
Generic Deployment Command Scenarios, and specify the
-Dkeywords=reverse
option
Configuration handlers are used to configure and unconfigure a XML Web Services 2.3 implementation during the certification process. These are similar to deployment handlers but used for configuration. A configuration handler is an Ant build file that contains at least the required targets listed below:
config.vi
- to configure the vendor implementation
clean.vi
- to unconfigure the vendor implementation
These targets are called from the <TS_HOME>/bin/build.xml
file and
call down into the implementation-specific configuration handlers.
To provide your own configuration handler, create a config.vi.xml file
with the necessary configuration steps for your implementation and place
the file under the <TS_HOME>/bin/xml/impl/<your_impl>
directory.
For more information, you may wish to view <TS_HOME>/bin/xml/impl/glassfish/config.vi.xml
,
the configuration file for Eclipse EE4J Jakarta EE 8 Compatible Implementation, Eclipse GlassFish.
Deployment handlers are used to deploy and undeploy the WAR files that contain the tests to be run during the certification process. A deployment handler is an Ant build file that contains at least the required targets listed in the table below.
The XML Web Services TCK provides these deployment handlers:
<TS_HOME>/bin/xml/impl/none/deploy.xml
<TS_HOME>/bin/xml/impl/glassfish/deploy.xml
<TS_HOME>/bin/xml/impl/tomcat/deploy.xml
The deploy.xml
files in each of these directories are used to control
deployment to a specific container (no deployment, deployment to
the Eclipse GlassFish Web container, deployment to the Tomcat Web container)
denoted by the name of the directory in which each deploy.xml
file
resides. The primary build.xml
file in the <TS_HOME>/bin
directory
has a target to invoke any of the required targets (-deploy
, -undeploy
,
-deploy.all
, -undeploy.all
).
To deploy tests to another XML Web Services implementation, you must create a custom handler.
Create a new directory in the <TS_HOME>/bin/xml/impl
directory tree.
For example, create the <TS_HOME>/bin/xml/impl/my_deployment_handler
directory.
Replace my_deployment_handler with the value of the impl.vi
property that you set in Step 5 of the configuration procedure
described in Section 4.2, "Configuring Your Environment to Repackage
and Run the TCK Against the Vendor Implementation".
Copy the deploy.xml file from the <TS_HOME>/bin/xml/impl/none
directory to the directory that you created.
Modify the required targets in the deploy.xml
file. This is what
the deploy.xml
file for the "none" deployment handler looks like.
<project name="No-op Deployment" default="deploy">
<!-- No-op deployment target -->
<target name="-deploy">
<echo message="No deploy target implemented for this deliverable"/>
</target>
<target name="-undeploy">
<echo message="No undeploy target implemented for this deliverable"/>
</target>
<target name="-deploy.all">
<echo message="No deploy target implemented for this deliverable"/>
</target>
<target name="-undeploy.all">
<echo message="No undeploy target implemented for this deliverable"/>
</target>
</project>
Although this example just echoes messages, it does include the four
required Ant targets (-deploy
, -undeploy
, -deploy.all
, -undeploy.all
)
that your custom deploy.xml
file must contain. With this as your
starting point, look at the required targets in the deploy.xml
files
in the Tomcat and Eclipse Glassfish directories for guidance as you create
the same targets for the Web container in which you will run your
implementation of XML Web Services.
The following Ant targets can be called from anywhere under the
<TS_HOME>/src
directory:
deploy
undeploy
deploy.all
undeploy.all
The deploy.all
and undeploy.all
targets can also be called from the
<TS_HOME>/bin
directory.
Note
|
The targets in the |
There are two general ways to run the XML Web Services TCK test suite using the JavaTest harness software:
Through the JavaTest GUI; if using this method, please continue on to Section 4.7, "Using the JavaTest Harness Configuration GUI."
In JavaTest batch mode, from the command line in your shell environment; if using this method, please proceed directly to Chapter 5, "Executing Tests."
You can use the JavaTest harness GUI to modify general test settings and to quickly get started with the default XML Web Services TCK test environment. This section covers the following topics:
Note
|
It is only necessary to proceed with this section if you want to run the JavaTest harness in GUI mode. If you plan to run the JavaTest harness in command-line mode, skip the remainder of this chapter, and continue with Chapter 5, "Executing Tests." |
In order for the JavaTest harness to execute the test suite, it requires information about how your computing environment is configured. The JavaTest harness requires two types of configuration information:
Test environment: This is data used by the tests. For example, the path to the Java runtime, how to start the product being tested, network resources, and other information required by the tests in order to run. This information does not change frequently and usually stays constant from test run to test run.
Test parameters: This is information used by the JavaTest harness to run the tests. Test parameters are values used by the JavaTest harness that determine which tests in the test suite are run, how the tests should be run, and where the test reports are stored. This information often changes from test run to test run.
The first time you run the JavaTest harness software, you are asked to specify the test suite and work directory that you want to use. (These parameters can be changed later from within the JavaTest harness GUI.)
Once the JavaTest harness GUI is displayed, whenever you choose Start, then Run Tests to begin a test run, the JavaTest harness determines whether all of the required configuration information has been supplied:
If the test environment and parameters have been completely configured, the test run starts immediately.
If any required configuration information is missing, the configuration editor displays a series of questions asking you the necessary information. This is called the configuration interview. When you have entered the configuration data, you are asked if you wish to proceed with running the test.
Before you start the JavaTest harness software, you must have a valid test suite and Java SE 8 installed on your system.
The XML Web Services TCK includes an Ant script that is used to execute the
JavaTest harness from the <TS_HOME>
directory. Using this Ant script
to start the JavaTest harness is part of the procedure described in
Section 4.7.3, "To Configure the JavaTest Harness to Run the
TCK Tests."
When you execute the JavaTest harness software for the first time, the JavaTest harness displays a Welcome dialog box that guides you through the initial startup configuration.
If it is able to open a test suite, the JavaTest harness displays a Welcome to JavaTest dialog box that guides you through the process of either opening an existing work directory or creating a new work directory as described in the JavaTest online help.
If the JavaTest harness is unable to open a test suite, it displays a Welcome to JavaTest dialog box that guides you through the process of opening both a test suite and a work directory as described in the JavaTest documentation.
After you specify a work directory, you can use the Test Manager to configure and run tests as described in Section 4.7.3, "To Configure the JavaTest Harness to Run the TCK Tests."
The answers you give to some of the configuration interview questions are specific to your site. For example, the name of the host on which the JavaTest harness is running. Other configuration parameters can be set however you wish. For example, where you want test report files to be stored.
Note that you only need to complete all these steps the first time you start the JavaTest test harness. After you complete these steps, you can either run all of the tests by completing the steps in Section 5.1, "Starting JavaTest," or run a subset of the tests by completing the steps in Section 5.2, "Running a Subset of the Tests."
Change to the <TS_HOME>/bin
directory and start the JavaTest test
harness:
cd <TS_HOME>/bin
ant gui
From the File menu, click Open Quick Start Wizard.
The Welcome screen displays.
Select Start a new test run, and then click Next.
You are prompted to create a new configuration or use a configuration
template.
Select Create a new configuration, and then click Next.
You are prompted to select a test suite.
Accept the default suite (<TS_HOME>/src
), and then click Next.
You are prompted to specify a work directory to use to store your test
results.
Type a work directory name or use the Browse button to select a work
directory, and then click Next.
You are prompted to start the configuration editor or start a test run.
At this point, the XML Web Services TCK is configured to run the
default test suite.
Deselect the Start the configuration editor option, and then click Finish.
Click Run Tests, then click Start.
The JavaTest harness starts running the tests.
To reconfigure the JavaTest test harness, do one of the following:
Click Configuration, then click New Configuration.
Click Configuration, then click Change Configuration.
Click Report, and then click Create Report.
Specify the directory in which the JavaTest test harness will write
the report, and then click OK.
A report is created, and you are asked whether you want to view it.
Click Yes to view the report.
The JavaTest GUI enables you to configure numerous test options. These options are divided into two general dialog box groups:
Group 1: Available from the JavaTest Configure/Change Configuration submenus, the following options are displayed in a tabbed dialog box:
Tests to Run
Exclude List
Keywords
Prior Status
Test Environment
Concurrency
Timeout Factor
Group 2: Available from the JavaTest Configure/Change
Configuration/Other Values submenu, or by pressing Ctrl+E
, the following
options are displayed in a paged dialog box:
Environment Files
Test Environment
Specify Tests to Run
Specify an Exclude List
Note that there is some overlap between the functions in these two dialog boxes; for those functions use the dialog box that is most convenient for you. Please refer to the JavaTest Harness documentation or the online help for complete information about these various options.
Previous | Next | Contents |