JDK-6508627 : 6u1 : Unable to send key events to AWT/Swing components embdedded inside Microsoft VB applications
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 6u1
  • Priority: P1
  • Status: Closed
  • Resolution: Duplicate
  • OS: generic
  • CPU: generic
  • Submitted: 2006-12-30
  • Updated: 2010-05-08
  • Resolved: 2007-01-10
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 6 JDK 7
6u1Resolved 7Resolved
Related Reports
Duplicate :  
Description
Using ActiveX Bridge functionality one can embed Java beans inside the Microsoft applications. Till 1.6.0 b105, one is able to send key events to these embedded beans but with 6u1 it's not happening.

Steps to reproduce:
1) Install 6.0 b105 and create axbridge/bin inside the JREHOME(C:/Progra~1/Java/jre1.6.0)
2) Copy the attached dlls(AXJTextArea.dll and AXTextArea.dll) into <jre_home>/axbridge/bin directory
3) Goto <jrehome>/axbridge/bin and execute 
  - regsvr32 AXJTextArea.dll
  - regsvr32 AXTextArea.dll
4) Execute the attached exe file.
5) Microsoft VB application with embedded AWT and Swing TextAreas should come up
6) Click on the buttons and try sending key events to the text areas. You should be able to write onto these TextAreas.
7) Close the application and unregister the dlls as follows
  - regsvr32 /u AXJTextArea.dll
  - regsvr32 /u AXTextArea.dll


Repeat the above steps with 6u1. With the 6u1 you can notice that both the text areas will not respond to the keyboard events

Comments
EVALUATION it is a duplicate of 6506966
10-01-2007

EVALUATION most likely this is a duplicate of 6506966
08-01-2007

EVALUATION This problem also affects applets in general. The attached MouseWheelApplet test case (self-documenting; see the .html file) shows that due to this bug it is no longer possible for an applet to receive the focus. This is an extremely serious regression especially since it is new in an update release. Raising this bug to a P1. The original fix for 6458497 should be backed out and rethought. This problem also affects the dolphin release. Created a SubCR for Dolphin.
05-01-2007

EVALUATION 6u1 nightly build dated 11/18/06 doesn't have this problem. The problem started surfacing on the next nightly build dated 11/22/06 with the windows-i586 bundles available. I've also found that the problem doesn't reproduce when using the awt.dll from 11/18 nightly with the 11/22 nightly build. This indicates that the problem was likely introduced by the fix for 6458497 in awt_Component.cpp. I'm transferring this CR to the awt team for further investigation.
03-01-2007