<AWT Dev> RFR:  JDK-8196681: Java Access Bridge logging and debug flags dynamically controlled
Sergey.Bylokhov at oracle.com
Mon Sep 17 21:52:36 UTC 2018
The "Java Access Bridge" as a product includes
WindowsAccessBridge-xx.dll and JavaAccessBridge-xx.dll.
On 17/09/2018 14:43, Krishna Addepalli wrote:
> Hi Sergey,
> Since the bug was about supporting Java Access Bridge Debugging, I have enabled logging only for Java Access Bridge. So, any log statements form Windows Access bridge are ignored.
> Do you think we should enable logging for Windows Access Bridge as well?
>> On 17-Sep-2018, at 11:12 AM, Sergey Bylokhov <Sergey.Bylokhov at oracle.com> wrote:
>> Hi, Krishna.
>> Can you please recheck how this logging will work when jab code will print something in parallel. As far as I understand libwindowsaccessbridge is loaded by the JAWS and libjavaaccessbridge by java, is it possibly that the log file will be garbled because of two libraries will print in parallel?
>> On 13/09/2018 12:25, Krishna Addepalli wrote:
>>> Hi All,
>>> Enhancement: https://bugs.openjdk.java.net/browse/JDK-8196681
>>> Webrev: http://cr.openjdk.java.net/~kaddepalli/8196681/webrev00/ <http://cr.openjdk.java.net/%7Ekaddepalli/8196681/webrev00/>
>>> Please review an enhancement for supporting the logging of Java Access Bridge, so that customers/users facing problems with Accessibility can turn on/off logging to debug problems with this feature.
>>> The proposed solution is to have the user/developer define an environment variable “*JAVA_ACCESSBRIDGE_LOGFILE*” and filling with the path to the log file.
>>> The JavaAccessBridge will read the variable, and write to the file in the path provided.
>>> Note that the implementation is simplistic, and doesnot have any way to handle multiple applications, since it is a debug only feature.
>> Best regards, Sergey.
Best regards, Sergey.
More information about the awt-dev