We are finding the case where it seems the Java JVM is bypassing standard Assistive Technologies bootstrapping when running the Selenium Standalone Server. This seems to happen regardless of launching the Grid/Server as a -jar or as a Class with appropriate -cp.
We have historically injected different varieties of test automation helper agents and functionality into the JVM. And this was working earlier in the year, but it now no longer works with the Selenium Server. It will work with other classes and JARS, but not the GridLauncher or SeleniumServer.
This is readily indicated by using (or creating) and enabling a Bogus Java Access Bridge Assistive Technology.
accessibility.properties file:
assistive_technologies=com.sun.java.accessibility.BOGUSAccessBridge
When a class specified as an Assistive Technology is specified and not found the JVM Exits the bootstrap process and stops. But it does not exit and stop when it is the Selenium Server that is being launched. It appears the entire Assistive Technologies (Accessibility Properties) bootstrap hook is bypassed during JVM initialization.
This proper behavior--both working and failure exiting--is properly demonstrated when using other JAR files or classes, but not the Selenium Server JAR file and classes.
We are currently using Java 7 JREs both 32-bit and 64-bit. Any info as to how to re-enable the JVM Assistive Technologies hooks in a Selenium Server JVM would be greatly appreciated.
Carl Nagle
Manager, Software Development
SAS Research and
Development
Quality User-driven Enterprise Software Testing
Automation Tools Group
Carl....@sas.com