JDK-4301272 : Propertychange event of JavaBean does not work properly in Visual Basic
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 1.2.2
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • OS: windows_nt
  • CPU: x86
  • Submitted: 1999-12-22
  • Updated: 2002-04-29
  • Resolved: 2002-04-29
Related Reports
Duplicate :  
Description

Name: sg39081			Date: 12/22/99


Apply the ActiveX bridge on a simple JavaBean with a bound property. The propertychange event only 
works properly when the bean is a visual component and is put inside a VB form. If the bean is a
 visual component but not put inside a VB form but instantiated via New, the propertychange event 
works badly. If the bean is a non-visual component the property change event works badly too.

In the UserForm of VBA/Excel2000 things are even worse: As visual bean in UserForm only now 
and then a propertychange event happens. As visual bean not put in UserForm or as non-visual
bean nothing happens. 

Also the bridge for JDK117B works better than the bridge of JDK12; the latter sometimes causes null pointer exceptions.
(Review ID: 88441) 
======================================================================

Comments
EVALUATION The Active-X Bridge was removed in Java 1.4.0 based on a Java Steering Committee decision nearly 2 years ago. The decision was based on 2 things. Customer interest was marginal at best and Java Plug-in was no longer dependent on the bridge technology to operate. It was necessary to remove it to allow for code refactoring and reworking in 1.4.0. Since removing the bridge, many customers have expressed interest in it. We have filed an RFE (4616580) for this support in a future release. We are currently evaluating whether we have a significant business case to justify the 1-3 man-month engineering effort (more for supporting teams) in the Mantis/Tiger timeframe. NOTE: Mantis = Java 1.4.2 FCS Q2, 2003 Tiger = Java 1.5 FCS Q4, 2003 Support for the bridge in existing 1.3.x releases is limited to escalations and can be persued with our CTE team. This bug will be closed as a duplicate of 4616580. ###@###.### 2002-04-29
29-04-2002