 |  |  |  |  |  |  |  |
| Version 8.0.1 |
Note JRE instrumentation has been obsolete for a long time now and can even cause problems. The following section remains only to provide background information and to show how to remove an existing JRE instrumentation without reinstalling the JRE.
Note To remove instrumentation of a JRE you need write permission for some of its directories, so you may have to work with administrator privileges to perform this step.
When instrumenting the JRE QF-Test made use of the official accessibility interface which is provided by Java for just this purpose. It can be used by accessibility and capture replay tools to interact with Java applications without those applications knowing about it and without requiring any changes to those applications.
To activate this interface, QF-Test created or modified the file
.../lib/accessibility.properties in the JRE installation and added the
class de.qfs.apps.qftest.start.Connector to the property
"assistive_technologies". This has the effect that this class will be instantiated
whenever the AWT toolkit is initialized in any Java application that is run
with this JRE.
To make sure that this class can always be found, the file qfconnect.jar which contains
the Connector class, was placed in the Java extensions directory .../lib/ext.
To deinstrument the JRE, first remove the entry for .../lib/accessibility.properties from the
"assistive_technologies" property in .../lib/accessibility.properties so that the Connector
class will no longer be used. Next delete the file qfconnect.jar from the
.../lib/ext directory of the JRE which is possible only when no Java program is currently being
run with this JRE.
| | | | | | | Last update: 9/10/2024 Copyright © 1999-2024 Quality First Software GmbH |
1. Functional cookies
We use functional cookies to ensure the basic functionality of the website.
2. Performance and statistic cookies
We use Matomo for analyzing and optimizing our website. Cookies permit an anonymous collection of information that help us offering you a clear and user-friendly visit of our web pages.
This cookie contains a unique, pseudonymized visitor ID internal to Matomo for recognizing returning visitors.
This cookie is used to track from which website the anonymized user proceeded to our website.
The Matomo session cookie is used to track the visitor's page requests during the session.
is created and should be then directly deleted (used to check whether the visitor’s browser supports cookies).
short lived cookies used to temporarily store data for the visit.
short lived cookies used to temporarily store data for the visit.
