# # Copyright (c) 2006, 2018 Oracle and/or its affiliates. All rights reserved. # # This program and the accompanying materials are made available under the # terms of the Eclipse Public License v. 2.0, which is available at # http://www.eclipse.org/legal/epl-2.0. # # This Source Code may also be made available under the following Secondary # Licenses when the conditions for such availability set forth in the # Eclipse Public License v. 2.0 are satisfied: GNU General Public License, # version 2 with the GNU Classpath Exception, which is available at # https://www.gnu.org/software/classpath/license.html. # # SPDX-License-Identifier: EPL-2.0 OR GPL-2.0 WITH Classpath-exception-2.0 # # # $Id$ # ######################################################################### # # # JavaTest Environment file for SAAJ Compatibility Test Suite # # # # Environment specific properties in this file will likely # # have to be modified prior to running the SAAJ TCK. Instructions # # for modifying these properties are contained in this file. # # # ######################################################################### #################################################################### ## When installing TCK/RI on Windows, users must install TCK and ## the RI on the same drive. Also note that you should never ## specify drive letters in any path defined in this properties ## file and all paths should be specified in the unix format only ## (ie. the "/" should be used instead of "\". #################################################################### #################################################################### # The following properties must be set prior to running the SAAJ # TCK tests. # # These web server properties must specify the host and port of # the web server in which the SAAJ TCK test servlets are deployed. #################################################################### webServerHost=localhost webServerPort=8080 ########################################################################### # local.classes should contain any RI specific jars/classes ########################################################################### local.classes=${web.home}/modules/webservices-osgi.jar:${web.home}/modules/endorsed/webservices-api-osgi.jar:${web.home}/modules/endorsed/jakarta.xml.bind-api.jar:${web.home}/modules/jaxb-osgi.jar:${web.home}/modules/jakarta.servlet-api.jar:${web.home}/modules/jakarta.ejb-api.jar #################################################################### # @endorsed.dirs If using JavaSE 8, verify that the property # endorsed.dirs is set to the location of the VI api jars # for those technologies you wish to overrride. JavaSE 8 # contains an implementation of SAAJ 1.3 which will conflict # with SAAJ 1.4, therefore this property must be set so that # SAAJ 2.2 will be used during the building of tests and # during test execution. For details regarding how the # Endorsed Standards Override Mechanism works, see # http://java.sun.com/javase/6/docs/technotes/guides/standards #################################################################### endorsed.dirs=${web.home}/modules/endorsed #################################################################### # The jars/classes for the TS harness/javatest and the test classes #################################################################### ts.harness.classpath=${ts.home}/lib/javatest.jar${pathsep}${ts.home}/lib/tsharness.jar${pathsep}${ts.home}/lib/saajtck.jar${pathsep}${ant.home}/lib/ant.jar${pathsep}${ts.home}/lib/jaxb-api.jar${pathsep}${ts.home}/lib/jaxb-xjc.jar${pathsep}${ts.home}/lib/jaxb-libs.jar${pathsep}${ts.home}/lib/jaxb-impl.jar ts.classpath=${local.classes}${pathsep}${ts.home}/lib/tsharness.jar${pathsep}${ts.home}/lib/saajtck.jar ts.run.classpath=${ts.home}/lib/tsharness.jar${pathsep}${ts.home}/lib/sigtest.jar${pathsep}${ts.home}/lib/saajtck.jar${pathsep}${ts.home}/classes${pathsep}${local.classes} ####################################################################################### # Implementation Property Settings for Vendor # # The TCK uses the following implementations: # - glassfish (JavaEE Web Container) # - tomcat (Tomcat Web Container) # # Here are the common properties that need to be defined for the common # implementation functionality: # # @impl.vi This property must be set to the Vendor implementation # under test. # @impl.vi.deploy.dir This property must be set to the deploy directory for # the Vendor implementation. # @impl.vi.host This property must be set to the webserver host where # the Vendor implementation is running. # @impl.vi.port This property must be set to the webserver port where # the Vendor implementation is running. # # These additional properties are required to be defined for use with configuration # functionality used for Vendor and RI specific configuration: # # @webcontainer.home This property must refer to the location of where the # Vendor implementation is installed within the webcontainer # under test (glassfish or tomcat). # @impl.deploy.timeout.multiplier The time it will wait for deployment to succeed # or fail ####################################################################################### webcontainer.home=${web.home} impl.vi=glassfish impl.vi.deploy.dir=${webcontainer.home}/domains/domain1/autodeploy impl.vi.host=${webServerHost} impl.vi.port=${webServerPort} impl.deploy.timeout.multiplier=120 #################################################################### # For the webcontainer home properties defined above, if glassfish # is selected these are the various additional properties that should # be set for use with configuration setup. #################################################################### # For glassfish as Vendor set the following: glassfish.instance.home=${webcontainer.home}/domains/domain1 glassfish.admin.host=localhost glassfish.admin.port=4848 glassfish.admin.user=admin glassfish.admin.pass= glassfish.master.pass=changeit glassfish.server.instance=server glassfish.domain.name=domain1 ######################################################################## ## Javatest batch mode work directory and report directory, and policy for ## handling existing work and report directories. These properties affects ## runclient and report targets, but not gui target. ## To disable generating test report, unset report.dir, or set it to "none" ## either here or from command line, as in the following command: ## ant runclient -Dreport.dir="none" ## # @if.existing.work.report.dirs specifies how existing work.dir and # @report.dir will be handled, and it must be one of the following values: # overwrite overwrites all content in work.dir and report.dir # backup moves all content in work.dir and report.dir to # work.dir_time_day_bak and report.dir_time_day_bak, # respectively # append reuses and preserves the existing work.dir and report.dir # auto lets the build files decide which mode to use # (overwrite, backup or append). the value is determined # like this: # if.existing.work.report.dirs == auto # if in CTS workspace # if.existing.work.report.dirs = overwrite # else we are in a distribution bundle # if.existing.work.report.dirs = append # end if # else # if.existing.work.report.dirs = value in this file # end if ######################################################################## work.dir=${ts.home}/../JTwork report.dir=${ts.home}/../JTreport if.existing.work.report.dirs=auto ############################################################### #These properties must be set to tell the Javatest harness the #class names of your porting class implementations. By default #the property settings below point to Sun RI specific classes. ############################################################### porting.ts.url.class.1=com.sun.ts.lib.implementation.sun.common.SunRIURL ######################################################################## ## These properties are used by the harness. "harness.log.port" ## specifies the port that server components use to send logging ## output back to JavaTest. If the default port # is not available ## on the machine running JavaTest, then you can set it here. ## ## "harness.log.traceflag" is used to turn on/off verbose debugging output ## for the tests. ## ## "harness.executeMode" is used to run the harness in the following modes ## of execution: ## 0 - default (deploy, run, undeploy) ## 1 - deploy only ## 2 - run only ## 3 - undeploy only ## 4 - deploy and run only ## # @harness.socket.retry.count - denotes the number of time we should # attempt to create a server socket when intilizing a test # client. The socket is used for logging purposes. ######################################################################## harness.temp.directory=${ts.home}/tmp harness.log.port=2000 harness.log.traceflag=true harness.log.delayseconds=1 harness.executeMode=2 harness.socket.retry.count=10 ############################################################### # Set your local timezone. For valid values, consult your Operating System # documentation. ############################################################### tz=US/Eastern ######################################################################## # @javatest.timeout.factor This property specifies the scale factor used by # Javatest to adjust the time JavaTest will wait for a given test to # complete before returning failure. For instance if the default test timeout # is 5 minutes, this value will be multiplied by 5 minutes to determine # the total timeout delay. Note: this value only works with Javatest's # batch mode (runclient). When using the Javatest GUI users must change # this timeout factor in the GUI. Configure -> Edit Configuration -> View # -> choose Standard Values -> select tab Execution -> set Time Factor. ######################################################################## javatest.timeout.factor=1.0 ####################################################################### #build level #platform mode is allways standalone ####################################################################### #1: compile only #2: compile and build component archives (e.g., jar's, war's) build.level=2 platform.mode=standalone ############################################################### # @ts.display -- location to display CTS output on Unix ############################################################### ts.display=:0.0 ####################################################################### # default deliverable class ####################################################################### deliverable.class=com.sun.ts.lib.deliverable.tck.TCKDeliverable ######################################################################## ## Common environment for both ts_unix and ts_win32 ######################################################################## command.testExecute=com.sun.ts.lib.harness.ExecTSTestCmd \ CLASSPATH=${ts.run.classpath} \ DISPLAY="${ts.display}" \ HOME="${user.home}" \ windir=${windir} \ SYSTEMROOT=${SYSTEMROOT} \ ${JAVA_HOME}/bin/java \ -Djava.security.policy="${bin.dir}/harness.policy" \ -Djava.security.manager \ -Djava.endorsed.dirs=${endorsed.dirs} \ -Ddeliverable.class=${deliverable.class} \ $testExecuteClass $testExecuteArgs ######################################################################### ## Environment for ts_unix ## The test execution commands inherit from common environment ## defined above: testExecute. ## If you need to override it, uncomment it in the following section. ######################################################################### env.ts_unix.menu=true ##env.ts_unix.command.testExecute= ######################################################################## ## Environment for ts_win32 ## The test execution commands inherit from common environment ## defined above: testExecute. ## If you need to override it, uncomment it in the following section. ######################################################################## env.ts_win32.menu=true ##env.ts_win32.command.testExecute= ######################################################################### # @sigTestClasspath: This property must be set when running signature # tests. This property should be set to a list of # jar files and/or directories which contain your # Java EE and Java SE classes. Paths must be # separated by the appropriate path separator # (';' windows, ':' Unixes). ######################################################################### sigTestClasspath=${local.classes}${pathsep}${java.home}/lib/rt.jar ############################################################### ## This command allows the test clients to be run in ## the same JVM as JavaTest in this case. This mode can be ## enabled by passing "-Dsame.jvm=true" to the runclient or gui ## targets. NOTE: This option is only to be used for sanity ## checking and not when running the TCK for compatibility. ############################################################### command.testExecuteSameJVM=com.sun.ts.lib.harness.ExecuteTSTestSameJVMCmd \ $testExecuteClass $testExecuteArgs ###################################################################### ## Deliverables must set this property to the name of the deliverable ## specific library jar file (iff create.manifest.extension.entries ## is set to true) ###################################################################### tslib.name=saajtck impl.vi=glassfish web.home=${ts.home}/../glassfish5/glassfish