-
Notifications
You must be signed in to change notification settings - Fork 26
Renaming Toolkit
For most of its life Toolkit has been delivered as xdstools2.war and was expected to be installed using that name. The resulting servlet context name was xdstools2 and the typical URL for launching was http://hostname:port/xdstools2.
One of the reasons this name was important was that the base URL of toolkit was built into the endpoints of simulators. The hostname and port were extracted from toolkit.properties and the context name was assumed to be xdstools2. This has been updated.
The hostname and port are still configured in toolkit.properties since they cannot be automatically extracted from the runtime environment. The context name is detected at runtime. More specifically, at startup, the context name is detected and the hostname and port from toolkit.properties are collected. Existing simulator configurations are scanned and their endpoints are updated. So if you are using simulators in your work, and the Conformance Test Tool automatically uses them, if you reconfigure Tomcat the simulators will be automatically reconfigured.
Toolkit
Downloads
Installing Toolkit
Configuring Toolkit for Imaging Tests
Reporting Toolkit Installation Problems
Environment
Test Session
Conformance Test Tool
Writing Conformance Tests
Overview of Imaging Tests
Test Context Definition
Launching Conformance Tool from Gazelle
Inspector
External Cache
Support Tools
Test Organization
Configuring Test Kits
Managing Multiple Test Kits
SAML Validation against Gazelle
Renaming Toolkit
Toolkit API
Managing system configurations
Configuring Toolkit for Connectathon
Developer's blog