The Java Access Bridge version 1.0 is a technology where the Java Accessibility API, commonly known as JAAPI is exposed in a Microsoft Windows DLL.
It is always recommended to install the Java Access Bridge 1.0 by using Java Access Bridge installer. This is because, the installer will locate the Java VMs needed to support the Java Access Bridge, that are installed on your computer. The Java Access Bridge installer then installs the Java Access Bridge into those Java VMs which are specified by you. Usually the Java Access Bridge installer can be found in the following directory:
c:\AccessBridge-1_0_2fcs\installer\Install.exe
The package of Java Access Bridge 1.0 contains three editions of Java Accessibility Utilities file ‘jaccess.jar’, named jaccess-1_1.jar, jaccess-1_2.jar, and jaccess-1_3.jar. One important thing that should be noted is that, you need to add the ‘AccessBridge-1_0’ directory to your path, in order to find and instantiate the two DLLs that are part of the Java Access Bridge 1.0.
A number of changes and improvements of the installer have been invoked in this version of Java Access Bridge. The menu timing problem that existed with Java 2 SDK 1.3 which resulted in the corruption of Java Access Bridge data stream have been resolved in this version of Java Access Bridge. Now there is no crashing when calling shutdownAccessBridge () from the Windows assistive technology. The installer has been modified. The ‘Install’ button is now only active when a JVM is selected to install into. Moreover, there is an addition of new button named ‘Install in All’. The function of this new button is to install the Java Access Bridge into all of the Java VM’s shown in the dialog box. Now there is no return of meaningless values by GetAccessibleTextRect() for carets at the edge of a line. The improved installer of Java Access Bridge 1.0 is now able to work with JDK 1.3.1_01 and 1.4.
Pros
- The installer works with JDK 1.3.1_01 and 1.4 now
- GetAccessibleTextRect() now returns actual values for carets at the edge of a line
- JAWS can now read Swing apps under JDK 1.4
Cons
- The installer may sometimes hang while enumerating the Java VMs installed
- on your computer
- Registering, unregistering, and then registering again for various of the menus and events might result in receiving of duplicate copies of the event
- You might not receive MenuCanceled or PopupMenuCanceled events. In order to determine that a menu has closed, you have to look for MenuDeselected events
- If you are using Java 2 SDK v1.4.x with JAWS for Windows, at least up to and including version 4.0, the Java application will cause a crash while exiting